-
Notifications
You must be signed in to change notification settings - Fork 54
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
[tests]: equivalent path templates are created #8
Comments
This is something we can actually detect while parsing. My initial thought was to emit a warning that it exists. Is it more surprising to have an auto-fix or to prompt for manual post-processing? |
I think you're right, maybe a warning. In APIs.guru we have an extension |
Not an easy one to solve. Shows up in the
fastly
fixture where pathItem keys end either {name} or {old_name}. If you replace each path template section with {0}, {1}, {2} etc and compare the resultant keys, duplicates are found.Some tools (cough) append a dummy fragment id to disambiguate equivalent pathItem keys.
The text was updated successfully, but these errors were encountered: