-
Notifications
You must be signed in to change notification settings - Fork 325
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Issue #627 custom message for format #632
Conversation
It looks good to me. It will be very useful for other users. Would you be able to create a document in the doc folder? Thanks. |
@stevehu I have updated document for custom messages with example and details, please check. |
@vickyrathod Thanks a lot for your help. |
How to specify custom message for required field?? |
I think that is standard. something like field name is required. |
This doesn't work for "required" key, standard message pop up |
This keyword doesn't support customized message as it is not necessary. |
I agree when you have to validate a simple JSON object. But what about nested objects? This schema: {
"type": "object",
"required": ["name"],
"additionalProperties": true,
"properties": {
"name": {"type": "string"},
"foo": {
"type": "object",
"uniqueItems": true,
"properties": {
"name": {"type": "string"}
},
"required": ["name"],
"additionalProperties": true
}
}
} with this JSON (missing {
"name": "lorem",
"foo": {"bar": "foobar"}
} The message for the nested |
No description provided.