Open MikeRalphson opened 4 years ago
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 x-hasEquivalentPaths
(https://github.com/APIs-guru/openapi-directory/wiki/specification-extensions#x-hasequivalentpaths) which we use to tag the output of other converters (like Google discovery format) to indicate we can suppress the validation error if needed.
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.