test(integration): verify that duplicated directives are not firing

[pkozlowski-opensource]

I wasn't sure if we've got some mechanism in place to avoiding matching all the directives specified in the @View annotation, so add a test. We might easily get into duplicate directives situation, as soon as we start to include coreDirectives in the @View by default.

Not sure if this test is mandatory, but I couldn't find the place where we filter out duplicates....

[tbosch]

Please rebase

[pkozlowski-opensource]

@tbosch I've rebased this one but now, after the rebase, it looks like the tested use-case doesn't work any more - that is - the test discovers a real bug! I will take a look at the underlying cause.

[tbosch]

@pkozlowski-opensource Could you investigate a little more why this is a problem?

[pkozlowski-opensource]

@tbosch I'm afraid I will need some input from you on this one, see #2756 (comment)

Will ping you later today.

[pkozlowski-opensource]

@tbosch rebased and fixed code to remove duplicate directives as discussed yesterday. We are applying very similar logic to the one in the injector

PTAL

BTW, build is failing due to the NPM install issues, nothing to do with this PR...

[tbosch]

Could you add one more test (just for a future reader) that states: 'It should use the last directive binding per directive'?

[pkozlowski-opensource]

@tbosch added a test. Is there anything else I should add or is this one good to go?

[tbosch]

Please merge!

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}