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
Could you please teach me one thing in Vue.js development?
Our project has SASS preprocessor set up and re-uses the same classes across different components.
According to a best practice in React componentizing (https://create-react-app.dev/docs/adding-a-sass-stylesheet/), the approach mentioned above is not recommended and I also found that such an approach might make it difficult to maintain the project.
Is it also true in Vue.js world?
The text was updated successfully, but these errors were encountered:
@anton-karlovskiy I would personally only put reset CSS in a global CSS context. I would put other classes in the components that use them - or use CSS modules to share styles across components in exceptional circumstances.
In most cases the latter isn't required - having good design tokens that can be referenced through variables throughout the codebase brings the required consistency.
In most cases the latter isn't required - having good design tokens that can be referenced through variables throughout the codebase brings the required consistency.
@pi0 @danielroe
Could you please teach me one thing in Vue.js development?
Our project has
SASS
preprocessor set up and re-uses the same classes across different components.According to a best practice in React componentizing (https://create-react-app.dev/docs/adding-a-sass-stylesheet/), the approach mentioned above is not recommended and I also found that such an approach might make it difficult to maintain the project.
Is it also true in Vue.js world?
The text was updated successfully, but these errors were encountered: