fix: issue with example URL query string in README.md and added documentation for validating request path parameters #121
Conversation
This file contains 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
Line 214 exemplifies the use of validating query string URL parameters using the library. However, the example was using the wrong query string parameter - "uuid", whereas the preceding JSON schema (tokenSchema) starting from line 188, was checking for a property called "token".
Currently, there is no documentation/example on how one could go about validating request path parameters, even though the library supports this. Added an example for the same.
snnair
changed the title
|
Hi @simonplend, please let me know if this is fine, or if I need to add any specific descriptors to the documentation text. |
simonplend
approved these changes
Mar 14, 2024
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.
Line 214 exemplifies the use of validating query string URL parameters using the library. However, the example was using the wrong query string parameter - "uuid", whereas the preceding JSON schema (tokenSchema) starting from line 188, was checking for a property called "token".