-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
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
CDN hosted version not working #14
Comments
There's an issue with Spectral not following redirects via |
@philsturgeon Thanks for a README update. There is no 1.3.1 version for @stoplight/spectral-owasp-ruleset, though. Example should be echo 'extends: ["https://unpkg.com/@stoplight/spectral-owasp-ruleset@1.1.1/dist/ruleset.js"]' > .spectral.yaml instead. |
Thanks, copy and paste mistake. Fixed that. |
Hello, I'm having this same issue except I can't get either of the suggested .spectral.yaml extends lines to work. echo 'extends: ["https://unpkg.com/@stoplight/spectral-owasp-ruleset@1.1.1/dist/ruleset.js"]' > .spectral.yaml I loaded the suggested CDN from the readme spectral lint .\openapi.yaml The following error occurs:
Now attempting to use the npm version echo 'extends: ["@stoplight/spectral-owasp-ruleset"]' > .spectral.yaml spectral lint .\openapi.yaml The following error occurs:
The NPM ruleset also failed Let me know if you want any more information. Perhaps I missed something? |
@Eddoson My guess is you have a Try spectral lint .spectral.yaml .\openapi.yaml to make sure you use right file. But I might be completely wrong. |
@vanam You fixed it! Thank you very much. I deleted the .spectral.yaml entirely and created a brand new file and pasted in the extends code rather than using |
I am also having the same problem but a different error. I added the Any clue of that? |
Current Behavior
If my
.spectral.yml
looks likeas you write in your documentation I get following error.
The same happens if I use your Docker image.
If I install
@stoplight/spectral-owasp-ruleset
package and my.spectral.yml
looks likeit works as expected.
Environment
The text was updated successfully, but these errors were encountered: