Open elize-vdr opened 1 year ago
Honestly, I didn't even think we had implemented $ref in PathItems, never mind external references here. I'm not sure we are likely to get a chance to fix this before the v2 release. If you have an idea how to fix it, we would be happy to take a PR for it.
Thank you for the feedback. I took a stab at implementing where a path is an external reference, please see PR https://github.com/microsoft/OpenAPI.NET/pull/1246
Describe the bug When reading and parsing an OpenAPI document with the OpenApi.Net library and there is a Path is a reference to another Path in another document where the path contains segments and therefore contina forward slashes between path segments, these have to be escaped with
~1
in the Path reference and the OpenApi library cannot resolve these.To Reproduce Parse the attached example with this OpenAPI.Net library.
Expected behavior When a Path is a reference to a path in another file then the forward slashes in th path is escaped with
~1
, the reference should be resolved to the correct path in the other file, currently it cannot be resolved.Screenshots/Code Snippets The reference in file (see attached) registration_v4.yaml is:
And the Path definition in the file common-definitions_v4.yaml is:
EXAMPLE registration_v4.yaml
common-definitions_v4.yaml