Multiple directives [arValidations, datepickerPopup] asking for new/isolated scope on...

[Alex Cips]

Reposting this question http://stackoverflow.com/questions/29636120/multiple-directives-arvalidations-datepickerpopup-asking-for-new-isolated-sco

I can think about workarounds but nothing simple. I feel there has to be a simpler way to get the same result.. it s just input validations.

[Sander Elias]

Hi Alex,

Why aren't you adding your validator(s) to ngModel.$validators? You are adding a lot of overhead + an extra watcher that is not really needed.

Regards

Sander

[Sander Elias]

Hi Alex,

As an addition to my other reply.

If you need multiple directives with each of them their own private stuff, create directives with controllers. For validation you don't need to sue $scope at all, but instead interface with ngModelController directly.

have a look at this directive example I created yesterday. It uses ngModel to get/set the scope variable, without ever touching the scope. The only time it uses scope is to propagate a new 'keyboard' to the view.

I use a $digest in there because there are only directive-local changes, and nothing else can be touched. 

Regards

Sander

[Alex Cips]

I didn't like the default validators so I built my own. The workaround I found was to build a custom datepicker directive that includes the 3rd party datepicker directive and adds validations to it.

[Sander Elias]

Hi Alex

You can add your OWN validators in there. you don't need tu use the default ones.

your code is mimicking the exact same thing as the error-handler of angular.

Regards

Sander