This repository was archived by the owner on Nov 8, 2024. It is now read-only.
fix: allow special characters on path parameters #2156
Conversation
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
Parsing openapi3 files encodes parameter names, that causes the tests that uses this kind of parameters being skipped.
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Parsing openapi3 files encodes parameter names, that causes the tests that uses this kind of parameters being skipped.
🚀 Why this change?
openapi3 is not allowing url parameters with special characters, the endpoints are skipped.
📝 Related issues and Pull Requests
#1908
✅ What didn't I forget?
npm run lint