Repository navigation
fix: fail validation when a runtime operation is undocumented - #189
Merged
Merged
Conversation
An implemented route missing from OpenAPI was a warning, so flexdoc validate exited successfully unless CI opted into --fail-on warning. That disagreement is the check this cycle exists to run. It is now an error, the derived status is fail, and the default CLI policy exits 1 while naming the method and path. Duplicate registrations stay warnings. Signed-off-by: Vishnu R <vishnurajesh45@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
fail, soflexdoc validateexits 1 under the default policy and the log names the method and path.Test plan
POST /internal/reindexexits 1 and the output names that operation