-
Notifications
You must be signed in to change notification settings - Fork 31
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
Fix request for spectral linter #270
Comments
@ahokkonen it doesn't look like that PR quite worked. The message is now: |
@cookeac legendary- working on my machine :) |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Attempt to fix Spectral paths. Resolves #270
Another attempt to fix the spectral ruleset problem. Resolves #270
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
I've encountered this one as well (and it still seems to be an issue). In my branch, I've fixed the paths but I get this very descriptive error message:
No clue how to continue along this path. Now testing with a default spectral github action (instead of relying on that docker image). |
Yep, the action does work (but now fails with proper validation errors). I'll create a pull request. |
Well... it does a bit more but I have no clue where it leaves its output. Maybe we should simply remove it and rely on speccy only? |
The speccy validations fails also by the way, but that doesn't stop the build (and still gives a green light..) |
At our meeting 2022-08-25 we agreed:
|
I found that spectral gives an incorrect error about an invalid array item type. I have installed the spectral validator component into VS Code and used it to clean up files before doing a PR/merge. |
New version of spectral linter requires ruleset parameter.
Creating default ruleset as part of the sources to solve that issue.
The text was updated successfully, but these errors were encountered: