A question: why have you chosen to use ViewEncapsulation.None in your schematics? This loses the capability to restrict class styles to a per component basis?
zpydee
All 3 comments
I agree (especially since NX creates a monorepo containing any number of components whose styles could collide with one another). where style collisions . I think that we should default to using ViewEncapsulation.Emulated personally
mrmeku
on 11 Dec 2017
I think this came over from a copy of the schematics option from the Angular CLI at the time when that was configured in there as a default (something that has been fixed in the Angular CLI). We just need to update the Nx schematic to remove that "default": "None" property.
https://github.com/nrwl/nx/blob/master/packages/schematics/src/collection/app/schema.json#L40
jschwarty
on 13 Dec 2017
From what I've experienced, it only places the ViewEncapsulation.None on the app.component.ts in the root of each of your apps.
ankemp
on 13 Dec 2017
Related issues
SWGeekPD
路
3Comments
about-code
路
3Comments
joelmuskwe
路
3Comments
IonFoXx
路
3Comments
olakara
路
3Comments
Most helpful comment
I agree (especially since NX creates a monorepo containing any number of components whose styles could collide with one another). where style collisions . I think that we should default to using ViewEncapsulation.Emulated personally