chore: make compatibility mode work for apps with multiple modules

[jelbourn]

R: @kara

The way I previously had the compatibility mode set up, it wouldn't have worked for applications that are composed of multiple NgModules because the sub-modules wouldn't have included the MdPrefixEnforcer directive.

For this new way, you're always going to have one of the prefix-enforcer directives loaded, but not the other.

[jelbourn]

@kara rebased and updated
@andrewseguin can you also take a look at this?

[andrewseguin]

Looks good to me. Curious that we have that list of selectors, is that to be maintained by us whenever we add/remove component selectors?

[kara]

LGTM

[kara]

Nit: From the name, I originally thought that this would enforce that you only had mat- prefixes, rather than you can't have mat- prefixes (as in, you're enforcing that they're present). I think it's the word "Enforcer". "MatPrefixRejector"?

[jelbourn]

Renamed

[kara]

Cool, LGTM (although it was LGTM before too)

[mmalerba]

please rebase

[mmalerba]

whoops, tried using the github button to resolve but that was apparently a bad idea, now it complains about merge conflicts when I try to g3sync presubmit.

@jelbourn is this something that can be fixed or do i just have to manually sync it now?

[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.}