-
-
Notifications
You must be signed in to change notification settings - Fork 233
-
-
Notifications
You must be signed in to change notification settings - Fork 233
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
Invalid JSON + invalid OAS is not recognized as such #2641
Comments
just a few thoughts
|
@daniel-white Thanks for your response!
|
It's just code. As Daniel mentioned, the tool should probably say something if it doesn't match on oas, aas, or json schema. Outside of that, there's not much to do. |
@mnaumanali94 do we have any use-cases for "passing through unknown spec files as error free"? I would consider throwing an error if spectral can't identify the specification? Couple of ways we can improve this:
|
Discussed in #2630
Originally posted by bereg2k June 2, 2024
Hello!
I have an invalid JSON which is invalid OAS too, but linting it doesn't report any errors:
invalid_spec.json
,
without any other members (invalid JSON)"openap"
instead of"openapi"
(invalid OAS)"paths"
(invalid OAS).My ruleset is...
.spectral.yaml
The output is:
What am I doing wrong here?
The text was updated successfully, but these errors were encountered: