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 docs/endpoints/schemas/get-employee.json is invalid
error: nullable value must be ["boolean"]
but unlike the other schema validation error messages, there is no hint as to where this error is coming from. It turned out that I had accidentally added nullable: "true" (this was a typo) in just one of the 100+ instances of nullable. This was extremely hard to find, and the error message didn't make it clear what the problem was in the first place.
Also, a suggestion to make the error message a bit easier to understand:
nullable value type must be one of ["boolean"] or just nullable value must be of type boolean (seems to be no reason to include a confusing array if there is only one possible type). Even better: nullable value must be of type boolean, not string
The text was updated successfully, but these errors were encountered:
I got this error:
but unlike the other schema validation error messages, there is no hint as to where this error is coming from. It turned out that I had accidentally added
nullable: "true"
(this was a typo) in just one of the 100+ instances of nullable. This was extremely hard to find, and the error message didn't make it clear what the problem was in the first place.Also, a suggestion to make the error message a bit easier to understand:
nullable value type must be one of ["boolean"]
or justnullable value must be of type boolean
(seems to be no reason to include a confusing array if there is only one possible type). Even better:nullable value must be of type boolean, not string
The text was updated successfully, but these errors were encountered: