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
...
27:20 error oas3-valid-schema-example "example" property must match format "uri" components.schemas.PaginatedAPNSDeviceList.properties.next.example
this is caused by " in example. (same arror can happen with oas3-valid-media-example)
Expected behavior
other yaml libraries (eg. pyyaml) recognize not-leading double quote and treat the value like a string, so it should not fail the validation (since format: uri gets downgraded to type: string, which should match, and if format: uri is recognized it should be valid anyway)
The text was updated successfully, but these errors were encountered:
Thanks @pomali do you know if (and which) part of the YAML specification non-leading quotes may be part of?
I'm not even sure if it's part of specification, but seems reasonable that linter should be able to read such malformed yaml, or throw some better error.
My guess would be that it's interpreted as Flow Plain Style so double-quote " has no special meaning there, but I'm just casual yaml user.
Describe the bug
when linting yaml file, value containing double quote
"
does not get recognized as stringTo Reproduce
a.yaml
and
.spectral.yaml
spectral lint a.yaml
this is caused by
"
in example. (same arror can happen with oas3-valid-media-example)Expected behavior
other yaml libraries (eg. pyyaml) recognize not-leading double quote and treat the value like a string, so it should not fail the validation (since format: uri gets downgraded to type: string, which should match, and if format: uri is recognized it should be valid anyway)
The text was updated successfully, but these errors were encountered: