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
When command prance validate reports a problem, it would be helpful for it to show which part of the document the error relates to, ideally with a line number, but failing that
If I intentionally make a yaml schema invalid, e.g. by changing a type: integer to type: unknown, then prance validate --backend openapi-spec-validator foo.yaml dumps out a large json representation of the schema (maybe a subset of the schema, but it was too big to diagnose) without any line breaks, despite the input being yaml, and thus no line number to indicate the problem.
The error seen at #133 indicates that using the flex backend probably also doesnt show line numbers.
If the backends, especially openapi-spec-validator, don't provide enough information for prance to be able to show better error diagnostics, then perhaps enhancements could be filed in those projects in order to allow this.
Minimal Example Spec
Actual Behaviour
Steps to Reproduce
Environment
OS: openSUSE Tumbleweed Linux
Python version: 3.10
Swagger/OpenAPI version used: 3.0
Backend: flex and openapi-spec-validator
The text was updated successfully, but these errors were encountered:
Expected Behaviour
When command
prance validate
reports a problem, it would be helpful for it to show which part of the document the error relates to, ideally with a line number, but failing thatIf I intentionally make a yaml schema invalid, e.g. by changing a
type: integer
totype: unknown
, thenprance validate --backend openapi-spec-validator foo.yaml
dumps out a large json representation of the schema (maybe a subset of the schema, but it was too big to diagnose) without any line breaks, despite the input being yaml, and thus no line number to indicate the problem.The error seen at #133 indicates that using the flex backend probably also doesnt show line numbers.
If the backends, especially
openapi-spec-validator
, don't provide enough information for prance to be able to show better error diagnostics, then perhaps enhancements could be filed in those projects in order to allow this.Minimal Example Spec
Actual Behaviour
Steps to Reproduce
Environment
The text was updated successfully, but these errors were encountered: