-
-
Notifications
You must be signed in to change notification settings - Fork 0
ci: adds additional test cases #145
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
Conversation
BREAKING CHANGE: drop support for query and fragment being part of path Refs #145
@baywet I've create Feel free to issue this (or other) PR again that branch. All assumptions in this draft PR and tests should now be passing in expected manner. |
I went ahead with this PR and consolidated the test against the |
# [2.0.0](v1.7.0...v2.0.0) (2024-12-24) ### Bug Fixes * return support for trailing slash ([b2fa107](b2fa107)) ### Features * align ABNF grammar more with RFC 3986 ([4498f0f](4498f0f)), closes [#145](#145) * align grammar with OpenAPI specification ([fdb67cd](fdb67cd)) ### BREAKING CHANGES * drop support for query and fragment being part of path
🎉 This PR is included in version 2.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
These additional test cases are supposed to be a base for discussion.
Everything that are inserted as is: I think the ABNF + parsing logic is correct, it's just adding additional validation. Please double check.
Everything else in a NOTE "block": I think the ANBF + parsing logic is incorrect, please double check. Once we agree my suggestion is to evolve the ABNF and move those cases to the right section.