Skip to content

fix: path params must not contain any unescaped generic syntax characters #132

New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Merged
merged 4 commits into from
Mar 1, 2024

Conversation

Himenon
Copy link
Owner

@Himenon Himenon commented Mar 1, 2024

Summary

The value for these path parameters MUST NOT contain any unescaped "generic syntax" characters described by RFC3986: forward slashes (/), question marks (?), or hashes (#).

close: #131

Test Plan

@Himenon Himenon merged commit 9fa1ce9 into main Mar 1, 2024
@Himenon Himenon deleted the fix/path-params-encoding branch March 1, 2024 16:13
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Bug: path parameter should be encoded
1 participant