To make things clearer could you update the description? The current description doesn't describe a problem: it describes expected behaviour.
Right now the error message -- which I think is clear -- is autogenerated by the code enforcing the schema. What are you proposing? I'm not sure that we want to go down a path where we're creating specific code/messages for every possible schema validation failure.
Hi,
To make things clearer could you update the description? The current description doesn't describe a problem: it describes expected behaviour.
Right now the error message -- which I think is clear -- is autogenerated by the code enforcing the schema. What are you proposing? I'm not sure that we want to go down a path where we're creating specific code/messages for every possible schema validation failure.