resolve-ref Reference does not exist for paths that contain ~1
See original GitHub issueIf i put ~1 in an external reference, i am getting resolve-ref errors. The file does exist at the path, and other validators validate against this construct OK.
Reference does not exist.
109|
110| /v1/adapter/claim:
111| $ref: "v1/adapter/claim.oas3.yml#/paths/~1adapter~1claim"
Error was generated by resolve-ref rule.```
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (3 by maintainers)
Top Results From Across the Web
Fails to resolve correct path/filename for extended $ref #200
I am facing an issue where json-schema-ref-parser creates references that are not supported by AJV and AJV can therefore not resolve them (see...
Read more >Resolve $ref by relative file path - Stack Overflow
For this, my first intuition was $ref to a path relative to the current file. However, the json-schema way doesn't seem to have...
Read more >Using $ref - Swagger
According to RFC3986, the $ref string value (JSON Reference) should contain a URI, which identifies the location of the JSON value you are...
Read more >Troubleshoot broken references - Visual Studio - Microsoft Learn
In the Folder field, type the path of the folder that contains the item you want to reference, and then click the Add...
Read more >`.gitlab-ci.yml` keyword reference - GitLab Docs
You can't include local files through Git submodules paths. ... There must be at least one other job in a different stage. .pre...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Confirmed 0.12.4 fixes the issue. That was an amazingly fast fix. Thank you.
Fixed in
0.12.4