Thinking a bit more about this and what could possibly be done to make it more generic is maybe to have a common attribute that is bind to the result, then inside the validation I could use that result to validate. The new attribute would have to be name that could be re-used no matter what 3rd party addon you use.

Something like this maybe (where validation-result would be a new attribute)

<div 
    ng-dropdown-multiselect="" 
    options="example1data" 
    selected-model="example1model"
    validation="required"
    validation-result="example1model">
</div>

or your other 3rd party addon (with again the new attribute validation-result)

<tags-input ng-model="example1model"
    validation="required"
    validation-result="example1model">
</tags-input>

That might work and could still be generic with common attribute which Angular-Validation would know where to get his result and still be efficient I believe.
But what I need to see inside the validation-result is flat result value, that might not work properly for validation of a certain value if your scope model is actually returning an id or something else that is not a flat result, then Angular-Validation might not know what to do with it, so in this case you might not always bind the scope model.

Please give feedback

Integration with angularjs-dropdown-multiselect #66

Description

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions