-
Notifications
You must be signed in to change notification settings - Fork 404
Add option for templateManipulator to ignore specific ng-model #358
Comments
Very good. I like the suggestion. I'd be happy to pull this concept in. I'll try to get to it as soon as I am able. If you want to try your hand at a PR, see CONTRIBUTING.md and the changes will likely be around here: https://github.com/formly-js/angular-formly/blob/master/src/run/formlyNgModelAttrsManipulator.js#L17 |
Like with #343, I've created tests for this feature and I'm going to give someone a shot at contributing to open source for the first time :-) So I will only accept a PR from someone who's never contributed to open source before. Instructions:
I'm happy to hold your hand through this if you need help. Catch me on gitter. |
P.S. I've already developed the solution, I just haven't committed it because I want to give someone else a first shot at contributing to open source 👍 |
@douglas-mason committed this! Thanks! |
This will be released as soon as I'm able |
This has been officially released in |
Hi @kentcdodds, the fix for this breaks IE8 compatibility. |
Both :-) Thanks! |
…pport querySelectorAll(':not()')
Fix for #358 that works around the fact that IE8 does not support querySelectorAll(':not()')
Sometimes custom templates may involve multiple directives referring to the same
ng-model
. For example:In this situation, formly adds the same attributes to both the
input
anddatetimepicker
.We can tell the manipulator to skip ALL attributes using
skipNgModelAttrsManipulator
, but what we really want is to just ignore the one ondatetimepicker
.It would be great to be able to add an attribute to the actual element so it is ignored:
The text was updated successfully, but these errors were encountered: