You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are using sakai-ng to develop our PrimeNg application theme, as it's now the new way to do.
Sakai comes with a bunch of scss files (visible in src\assets\layout\styles\layout*), and this is ok.
The problem is those file are considered as anonymous layers and they have a bigger priority in the rendering process.
For example, using css custom layers while templating the h1 tag will never be rendered as expected because the applied rule will be the one specified in _typography.scss.
Adding a '@layer sakai' for all the files in src\assets\layout\styles\layout will be, I think, a good idea to prevent this behavior and let teams render has expected their styles.
The text was updated successfully, but these errors were encountered:
Hi,
We are using sakai-ng to develop our PrimeNg application theme, as it's now the new way to do.
Sakai comes with a bunch of scss files (visible in src\assets\layout\styles\layout*), and this is ok.
The problem is those file are considered as anonymous layers and they have a bigger priority in the rendering process.
For example, using css custom layers while templating the h1 tag will never be rendered as expected because the applied rule will be the one specified in _typography.scss.
Adding a '@layer sakai' for all the files in src\assets\layout\styles\layout will be, I think, a good idea to prevent this behavior and let teams render has expected their styles.
The text was updated successfully, but these errors were encountered: