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
Created a simple repo that helps explain the bug can be found here
Describe the bug Say you have the following structure
├── src │ ├── folder-a │ │ ├── schema-a.json │ │ ├── schema-b.json │ ├── folder-b │ │ ├── schema-c.json └── yourrules.spectral.yaml
If schema-b has a reference to schema-a and schema-a has a reference to schema-c and schema-c has a reference to itself, then if you were to run
schema-b
schema-a
schema-c
spectral lint src/**/*.json
you would have an invalid-ref error reported for schema-b, but if you were to instead run
invalid-ref
spectral lint src/folder-a/schema-b.json
no errors would be reported
To Reproduce
OR
npm run lint
Expected behavior No errors to be reported
Environment (remove any that are not applicable): Spectral: 6.11.0
Additional context See https://github.com/cvent/spectral-bug-example/blob/main/README.md for more details and thoughts on why bug is happening
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Created a simple repo that helps explain the bug can be found here
Describe the bug
Say you have the following structure
If
schema-b
has a reference toschema-a
andschema-a
has a reference toschema-c
andschema-c
has a reference to itself, then if you were to runyou would have an
invalid-ref
error reported forschema-b
, but if you were to instead runno errors would be reported
To Reproduce
spectral lint src/**/*.json
OR
npm run lint
Expected behavior
No errors to be reported
Environment (remove any that are not applicable):
Spectral: 6.11.0
Additional context
See https://github.com/cvent/spectral-bug-example/blob/main/README.md for more details and thoughts on why bug is happening
The text was updated successfully, but these errors were encountered: