[SERVER-32093] 3.6 $jsonSchema validator error message improvements Created: 27/Nov/17 Updated: 27/Nov/17 Resolved: 27/Nov/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 3.6.0-rc4 |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Trivial - P5 |
| Reporter: | Ken W. Alger | Assignee: | Unassigned |
| Resolution: | Duplicate | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Participants: | |||||||||
| Description |
|
When a document fails validation from a prescribed schema a WriteError is generated with a {{"code": 121, message. It would be great if the error message would be more explicit as to why the write failed, i.e. which rule was violated. Or, allow for an error parameter to be included in the schema validation rules to allow for custom messaging if a rule is violated, i.e. error: "Are you sure that you are passing in an 'int' value?". |
| Comments |
| Comment by Kyle Suarez [ 27/Nov/17 ] |
|
Hi kenwalger, Thank you for your improvement suggestion. We already have a request for this in Regards, |