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
Describe the bug
Spectral finds a problem; in this case, a $ref cannot be resolved. The extension properly shows valid problems
However, after I correct the paths for those $ref, Spectral does not remove the errors. It leave error items and text markers in the source.
$ref
Even closing the file and opening it again does not clear the problems view. I have to exit VS Code and restart.
Similarly, when Spectral adds a problem about an unused component, that problem persists even after adding a .spectral.yaml file containing
.spectral.yaml
extends: spectral:oas rules: oas3-unused-component: false
To Reproduce
unzip the attachment Even though the command
$ cd apis/common $ spectral lint -r .spectral.yaml openapi.yaml No results with a severity of 'error' found!
the VS Code view still shows the problems.
For this small example, the problem view does clear when I fix the $ref from
'401': $ref: '#/components/responses/401' '403': $ref: '#/components/responses/403'
to
'401': $ref: '../common/openapi.yaml#/components/responses/401' '403': $ref: '../common/openapi.yaml#/components/responses/403'
but in my working OpenAPI (3000+ lines) it does not refresh
Expected behavior
Clear errors for a file after the file has been edited and re-scanned.
Environment:
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Describe the bug
Spectral finds a problem; in this case, a $ref cannot be resolved. The extension properly shows valid problems
However, after I correct the paths for those
$ref
, Spectral does not remove the errors. It leave error items and text markers in the source.Even closing the file and opening it again does not clear the problems view. I have to exit VS Code and restart.
Similarly, when Spectral adds a problem about an unused component, that problem persists
even after adding a
.spectral.yaml
file containingTo Reproduce
unzip the attachment
Even though the command
the VS Code view still shows the problems.
For this small example, the problem view does clear when I fix the $ref from
to
but in my working OpenAPI (3000+ lines) it does not refresh
Expected behavior
Clear errors for a file after the file has been edited and re-scanned.
Environment:
stale-problems-view.zip
The text was updated successfully, but these errors were encountered: