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
Considering that schema and its extensions are attached to the resource on server creation, should any schema name validation be present? If so, then I'll be happy to implement this validation.
The text was updated successfully, but these errors were encountered:
We should indeed check this and not just ignore it, this is a bug.
By default we do ignore all fields that are not defined within the schema, but schemas is part of each schema be default.
I've noticed that if the client sends a resource creation request with an invalid schema, it reaches the HTTP handler:
Considering that schema and its extensions are attached to the resource on server creation, should any schema name validation be present? If so, then I'll be happy to implement this validation.
The text was updated successfully, but these errors were encountered: