Skip to content
New issue

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

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

Already on GitHub? Sign in to your account

[Bug] [OpenAPI 3.1] Path parameter values cannot contain the unescaped characters /, ? or # #6023

Open
wanlwanl opened this issue Feb 17, 2025 · 1 comment
Labels
bug Something isn't working emitter:openapi3 Issues for @typespec/openapi3 emitter triaged:core
Milestone

Comments

@wanlwanl
Copy link
Member

wanlwanl commented Feb 17, 2025

Compared to 3.0, path parameter values cannot contain the unescaped characters /, ? or #
For now, / and # are allowed.

Playground

@wanlwanl wanlwanl added the emitter:openapi3 Issues for @typespec/openapi3 emitter label Feb 17, 2025
@wanlwanl wanlwanl changed the title [OpenAPI 3.1] Path parameter values cannot contain the unescaped characters /, ? or # (need to double confirm) [OpenAPI 3.1] Path parameter values cannot contain the unescaped characters /, ? or # Feb 17, 2025
@wanlwanl wanlwanl added the bug Something isn't working label Feb 17, 2025
@wanlwanl wanlwanl changed the title [OpenAPI 3.1] Path parameter values cannot contain the unescaped characters /, ? or # [Bug] [OpenAPI 3.1] Path parameter values cannot contain the unescaped characters /, ? or # Feb 17, 2025
@markcowl
Copy link
Contributor

  • require url encoding in the path for (#)

@markcowl markcowl added this to the Backlog milestone Feb 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working emitter:openapi3 Issues for @typespec/openapi3 emitter triaged:core
Projects
None yet
Development

No branches or pull requests

2 participants