-
-
Notifications
You must be signed in to change notification settings - Fork 50
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
Empty strings in paths #583
Comments
looks like a glitch - so it looks like the spectral-report needs a tuneup. |
A double dot (deep search) will cause gaps in a spectral path property, this has been fixed. This is still not a full complete fix, because the JSON path for results is calculated by the doctor, and this looks like a straight passthrough from the rule, which needs further investigation.
A double dot (deep search) will cause gaps in a spectral path property, this has been fixed. This is still not a full complete fix, because the JSON path for results is calculated by the doctor, and this looks like a straight passthrough from the rule, which needs further investigation.
A double dot (deep search) will cause gaps in a spectral path property, this has been fixed. This is still not a full complete fix, because the JSON path for results is calculated by the doctor, and this looks like a straight passthrough from the rule, which needs further investigation.
Should be fixed in |
Thanks Dave, just tried v0.14.3 and I now get a different output, but there's still empty strings: [
{
"code": "define-magic-header",
"path": [
"paths",
"..",
"",
"responses",
"..",
"",
"headers"
],
"message": "Response is missing a magic header.: `MagicHeader` must be defined",
"severity": 0,
"range": {
"start": {
"line": 12,
"character": 13
},
"end": {
"line": 12,
"character": 13
}
},
"source": "my-openapi-spec.yaml"
}
] |
This is very odd. It’s not what I saw at all. I guess I need to dig deeper. It was a light weight fix that seems to be ineffective. |
Hey @daveshanley, have you been able to dig deeper? |
I have not sorry, I have been working on the doctor - which requires a lot of focus. Once the next version of the stack is released I will circle back on bugs for a while - they are stacking up a bit. |
Hey, thanks to #581 I've gotten my custom rule working.
Unfortunately I'm now facing an issue with the
path
property in the report containing empty strings.I'm running:
And here's all the assets:
custom-rules.yaml
my-openapi-spec.yaml
And then the resultant
spectral.json
:The text was updated successfully, but these errors were encountered: