User Story

As a Compass user
I want a quick and intuitive way to create schema validation rules
So that I don’t have to remember the validator syntax and I don’t have to type anything when what I need is really simple

Acceptance Criteria

• When I open the Validation screen, and the server I am connected to has version >= 3.6, I can choose to create/edit/delete my validation rules with a simple rule builder
• The simple rule builder allows me to create simple rules to support a limited number of common use cases (e.g. type of a field, min/max, enum, to be defined)
• Simple rules are created with an interactive mode rather than by typing code or JSON
• When rules are created with the simple rule builder, they are translated behind the scenes into a JSON Schema
• It should be possible to specify multiple rules for the same field
• It should be possible to specify that a document is valid only when all and only the fields that have been explicitly listed in the rules are present (i.e. allowAdditionalProperties: false is set for all the objects when the rules are translated into JSON Schema)
• When I attempt to save a rule and the rule is correctly saved, I want to see a confirmation message
• Rules are always and-ed
• When I attempt to save a rule and the rule cannot be saved or there is an error, I want to see an error message
  • This includes conflicts between rules detected by the server, or if we can detect that before saving even better
• When I create a rule for a field, the field name should be autocompleted if there are already existing documents in the active collection
• When I create a rule for a field, I should be able to type its name if it’s not already set for the documents already in the collection or if there are no documents in the collection

Notes

• The > 3.6 topic may change in case of some push backs during the scope doc review