We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
When using chips the structure of the model changes when an item is added or deleted.
The materialize chips component expects an array with a tag property like so: [{tag:'chip1'},{tag:'chip2'}]
[{tag:'chip1'},{tag:'chip2'}]
The initial binding works just fine but as soon as you add a new chip, angular.materialize.chips actually changes your model to: ['chip1','chip2']
['chip1','chip2']
This is the offending line: ad6a7fb#diff-002acb22231043b6342eac8068420c4cR145
scope.ngModel =element.data().chips.map(function (item) { return item.tag })
I think it should just be:
scope.ngModel = element.data().chips;
Example: http://jsfiddle.net/gmse4pgc/6/
The text was updated successfully, but these errors were encountered:
No branches or pull requests
When using chips the structure of the model changes when an item is added or deleted.
The materialize chips component expects an array with a tag property like so:
[{tag:'chip1'},{tag:'chip2'}]
The initial binding works just fine but as soon as you add a new chip, angular.materialize.chips actually changes your model to:
['chip1','chip2']
This is the offending line:
ad6a7fb#diff-002acb22231043b6342eac8068420c4cR145
scope.ngModel =element.data().chips.map(function (item) { return item.tag })
I think it should just be:
scope.ngModel = element.data().chips;
Example:
http://jsfiddle.net/gmse4pgc/6/
The text was updated successfully, but these errors were encountered: