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
Schema error at paths./brands.get.responses[200]
is not exactly one from <#/definitions/response>,<#/definitions/jsonReference>
Semantic error at paths./brands.get.responses.200.schema.properties.brands.items.properties.name.type
"type" should be a string
The second issue is being caused by the type: ["string", "null"] line but all my draft4 json schema specs are passing so I dont understand why its complaining? Is this not valid schema?
Regards.
The text was updated successfully, but these errors were encountered:
@robinsingh-bw Swagger doesn't use the full JSON Schema. One of the restrictions is that type must be a single value and not an array. null is not supported as a type at all.
Hey there! Sorry to bring this back up, but it's the sort of thing that's gonna get found on Google. It certainly is not a job for Swagger Editor to worry about htis, as Swagger Editor is just following the Swagger specification, but is there an issue somewhere where this is being worked on?
The whole "Meh we're a sub&super-set of JSON Schema is not an ok status quo, but an anomaly that needs to be eradicated one piece at a time. Right?
Hi,
I have the following schema:
Its showing these two errors:
The second issue is being caused by the type: ["string", "null"] line but all my draft4 json schema specs are passing so I dont understand why its complaining? Is this not valid schema?
Regards.
The text was updated successfully, but these errors were encountered: