Include shape name in REQUEST_URI_NOT_FOUND validation error message#6789
Open
Include shape name in REQUEST_URI_NOT_FOUND validation error message#6789
Conversation
|
RanVaknin
added
changelog-not-required
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
1 participant
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.
The
REQUEST_URI_NOT_FOUNDvalidation error inAddShapes.findRequestUriwas printing Optional.empty instead of the actual shape name, making it impossible to identify which shape caused the failure.This can occur when a shape has a member with
"location": "uri"but isn't directly referenced as an operation's input. The fix resolves the shape name from the model and includes it in the error message.