Compass
5 results found
-
Explain why "Document failed validation"
When saving a document fails, and the error "Document failed validation" is raised, it would be incredibly useful to know in what way the document does not match the validation schema.
There's a whole meme at my company about this error and the hours we waste chasing down the various causes.
Yes I'm aware of the "application validation" argument. We do it too. But we have big documents, big collections, and frequent schema migrations; there's going to be issues. Compass does not access MongoDb though our application, so it seems like the right place to be able to know "why".
…
12 votes -
Possibility to set variables used in pipeline stages
Hi !
It would be really handfull to have the possibility to use variables in the pipeline stages:var userId = ObjectId("5f61dfadc1e8960001700da8'")
{
$match : {user.id : userId}
}for complex queries, it would avoid having to modify the id at each stages.
Thanks !9 votes -
The JSON Schema export should be producing a jsonschema file that can be used immediately with schema validation
It currently dumps a bunch of analysis information even though the menu item is "Share Schema as JSON". This file is useless for trying to harden or define a schema, even in non-mongodb tools (like validating documents match schema in our programs).
4 votes -
Generate jsonSchema Validation Based on Schema Analysis
Since Compass already provides a schema analysis, it would be useful if that analysis could be used generate jsonSchema. The result could be a starting point for the Validation tab or used in other tools such as https://hamidihamza.com/Angular6-json-schema-form/.
4 votes -
Export data from a query should limit fields based on Projection
When exporting data from a query in MongoDB Compass, only check the fields that are in the Projection section. Don't default to all the fields when exporting.
3 votes
- Don't see your idea?