fix(schematics): do not allow specifying native view encapsulation

[devversion]

No longer allows developers to specify the --viewEncapsulation Native when creating components through the Angular Material schematics. Since Angular Material does not work properly with Native / ShadowDom view encapsulation, we should not support these as valid schematic options.

[jelbourn]

I don't know if this is a good idea; our theming doesn't work with native shadow DOM.

[devversion]

The option is just setting the ShadowDom encapsulation on the given component that has been created. The idea was to make everything consistent with the @schematics/angular:component schematic.

I see that we should probably not support this. If we don't want to go that way, even though it's kind of bad for consistency, we should also consider removing the Native view encapsulation from Angular versions before. Also do we have some notes on the README.md about this?

[devversion]

@jelbourn Addressed what we discussed in the standup. Though we do not have a good way of throwing an error because we need to handle the possible values through the schema.

Otherwise, tools that show the available options for a schematic (e.g. AngularConsole) will incorrectly display ShadowDom or Native as valid options.

[jelbourn]

LGTM

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