Timeline for How do I determine why a MongoDB document is failing validation?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 25, 2018 at 3:27 | comment | added | Stennie |
@HendyIrawan Yes, there are a few extensions to JSON Schema for MongoDB data types so additional client validation or transformation would be required for strict validation. I've seen a few examples like mongo-schemer for Node.js, which builds on AJV (Another JSON Schema Validator).
|
|
| May 24, 2018 at 8:55 | comment | added | Hendy Irawan | The problem is the schema format is "semi-standard" i.e. with MongoDB extensions, so it's still hard to find out what is the cause using standard JSON Schema validators. | |
| Aug 23, 2016 at 2:21 | comment | added | Jonathan Wheeler | Thanks! Guess I wasn't missing anything here. We indeed do most of our validation in our application, but we leave low-level checks as MongoDB validators, mostly to make sure our software engineers (and myself) aren't creating bugs during development, rather than to find user errors in production. I've up-voted the JIRA. Cheers! | |
| Aug 23, 2016 at 2:01 | vote | accept | Jonathan Wheeler | ||
| Aug 23, 2016 at 0:46 | history | answered | Stennie | CC BY-SA 3.0 |