create ordain module

[ng-druid]

The ordain module will provide the validation plugin manager and models.

https://github.com/rollthecloudinc/druid/issues/159

[ng-druid]

Completed:

• Create ordain module and wire up with current ci/cd workflow
• Create validation plugin manager
• Create core validator discovery that currently provides Angular required and min validators.
• Add validation form to form element editor including customizing validators with params.
• Save validation info as part of form element data object.
• Repopulate / restore validation form including params when editing existing form element with validation
• Create component to manage error messages. At the moment the error message is static but will become dynamic, customizable inside the validation editor.

Visual Aids

New Validation Editor

• Users can click "Add Validator" to add a new validator.
• Users can than optionally name and select a validator implementation (plugin).
• Once validator is selected any params (options) for the validator can be feed in as params.
• Params like many other parts of druid is designed to be specified as a query string with colon prefix representing "configurable, dynamic variables". Those configurable dynamic variables have access to a wide range of state within druid through the context system.

Issues

1. Validation status of form element not propagating up to panel page. This prevents detection of invalid form elements. The panelpage form is always valid since the status isn't making its way all the up the panel page hierarchy. (complete)
2. Users should be able to customize error messages and use tokens inside messages. Tokens will include access to available contexts and exposed values of validation.

Considerations

• To achieve the level of customization required for validation, specifically using params ALL validators require async operations. Therefore, the panel page render components have all been converted to async validators instead of standard validators. However, this isn't quite working yet. See first issue above.

[ng-druid]

Debugging Status Propagation:

• panel page
  • panel render
  • pane render
    • component renderer
    • component render propagates independent form control value and status manually through valueChanges and statusChange listener.

I seem to have been able to work my way around issue 1 above. This was achieved by doubling up the validation on both the proxy control and parent control. The proxy control uses the raw value where as the serialized value is being used to the parent settings form control. I made the builder function compatible with both these data type contexts by adding a serialized boolean to let the builder function know whether it is operating on raw data or serialized data.

Verified by hitting submit. console logs "detected invalid form" rather than persist of data. When form valid data is logged and persisted.

[ng-druid]

Task: Customized Error messages

At the moment a single static value inside a dedicated component. The editor will have text area to override and use tokens inside error messages.

Example: "At least [.min] characters required."

Where [.min] would be replaced by the validation return object (_root).min. The validation return object would act as the _root context when replacing tokens in error messages.

This is complete.

[ng-druid]

Idea:

Validator that integrates with avm (json schema). Accepts url to json schema file. Validator that can expand into multiple validators when being used on forms. For example, a json schema that expands into multiple validators. Would that even be needed?

This might be better of as a spell.

[ng-druid]

The mvp for forms validation is complete. Form elements on panel pages now have optional validation capabilities. Druid core supplies angular core validators. New validators can be added as plugins. Future features/integrations below.

• https://www.npmjs.com/package/ajv
• https://www.npmjs.com/package/jsonschema

Some trivial clean-up to follow before merge such as; reducing repeating code for resolving params.