You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Most of the time linting passes but occasionally (1 out of 4 runs or so) it results in an error for path $.components.schemas['ProblemDetails'].properties['invalidParameters'].items.properties['reasons'].items or $.paths['/test'].get.responses['200'].content['text/json'].schema.properties['invalidParameters'].items.properties['reasons'].items or similar ones (paths where the ignored path is $ref'd).
Is there any way to work around this and only show errors for the component itself but not paths and components that reference the one with the error? Even showing the same error for all references every time would help.
The text was updated successfully, but these errors were encountered:
I'm getting inconsistent results when linting the following spec
with only
owasp-string-restricted
enabled and this ignore fileMost of the time linting passes but occasionally (1 out of 4 runs or so) it results in an error for path
$.components.schemas['ProblemDetails'].properties['invalidParameters'].items.properties['reasons'].items
or$.paths['/test'].get.responses['200'].content['text/json'].schema.properties['invalidParameters'].items.properties['reasons'].items
or similar ones (paths where the ignored path is $ref'd).Is there any way to work around this and only show errors for the component itself but not paths and components that reference the one with the error? Even showing the same error for all references every time would help.
The text was updated successfully, but these errors were encountered: