Shared ng-models state for nested models #3612
Labels
enhancement
New value added to drive a business result
Team:Core
Core services & architecture: plugins, logging, config, saved objects, http, ES client, i18n, etc
As noticed in #3518 (comment), our number-list control uses multiple ng-models, causing it to feel like seperate inputs when it should feel like a single input.
Currently This is expressed in the markup by having an ng-model directive on the kbn-number-list directive. The template for that directive though creates several nested ng-models (one for each list item) and they all maintain individual state (valid, invalid, touched, etc.)
I think we need to make these changes:
The text was updated successfully, but these errors were encountered: