We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The linter fails if there are ~1 or ~2 tokens in a ref path, which are used as replacements for / if the / appears in the reference.
~1
~2
/
example:
paths: /v1/auth/newcustomer: # Causes a new customer email to be sent $ref: "v1/auth/newcustomer.yml#/paths/~1auth~1newcustomer"
is a valid reference to:
paths: /auth/newcustomer
in the v1/auth/newcustomer.ym file.
v1/auth/newcustomer.ym
however such a construct will yield a reference components should all match spec. regex error from the linter.
reference components should all match spec. regex
The text was updated successfully, but these errors were encountered:
Fix linting of escaped refs, #172 and #222
ae2d39a
Should be fixed in:
by only applying this rule to $refs which start with #/components/
$ref
#/components/
Sorry, something went wrong.
No branches or pull requests
Checklist
The linter fails if there are
~1
or~2
tokens in a ref path, which are used as replacements for/
if the/
appears in the reference.example:
is a valid reference to:
in the
v1/auth/newcustomer.ym
file.however such a construct will yield a
reference components should all match spec. regex
error from the linter.The text was updated successfully, but these errors were encountered: