-
-
Notifications
You must be signed in to change notification settings - Fork 240
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
URIError console warns #658
Comments
@philsturgeon Hey! Have you had the chance the repro the issue and/or triage it? I understand this might not be a high priority as this doesn't prevent Spectral from working, but those warnings greatly reduce the readability of the produced log and make it far more difficult to go through. |
@nulltoken taking a look 👀
It's actually a slight regression introduced in 4.2. Going to fix it and perhaps release a patch version once the fix is merged. |
@nulltoken sorry for the delay, this is definitely something that needs fixing sooner rather than later. It's the thick of conference season so im slow at replying, but the team are on point as always! :D @P0lip this seems like something which might have been hidden through --silent. Can we investigate other ways to silence the log output which was annoying us? Doesn't need to be done now, just keep it in mind. Either way im sure you can solve this regression easily enough! |
@P0lip Do you think this could be part of the next |
@nulltoken this will be a part of the next release, word. |
@P0lip 😍 |
Describe the bug
Linting a file that references another external file over http fills the console with unexpected warnings.
To Reproduce
repo/ruleset.yaml
repro/URIError.yaml
https://REDACTED/static/schemas/common/v2/library.openapi.yaml
The console is filled up with unexpected warnings
URIError: Invalid JSON Pointer syntax; URI fragment identifiers must begin with a hash.
Expected behavior
No warnings ;-)
Environment (remove any that are not applicable):
The text was updated successfully, but these errors were encountered: