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
Sometimes a consumer app might have a need to import all of the Sass variables and mixins available in the library at once, with no CSS build artifacts (such as classes or CSS variables) actually appearing.
This might be useful if you want to build a Veera-based component that the CVI library doesn't currently offer.
Having a single import for Sass entities will provide an easier upgrade path for consumer apps (internal paths of Sass files could be changed freely then).
What alternatives have you tried?
Right now it is impossible, you can only import both generated CSS and Sass artifacts mixed together or you can import Sass files one by one, which might be time-consuming and prone to breaking when upgrading a version of the library.
Does this feature request involve any updates to the reference design?
No
Implementation details
It should suffice to move imports for all Sass variables and mixins into one importable Sass file. We also would likely need to split files like colors.scss into a file with Sass data and another file dealing with the generation of CSS variables based on that data.
The text was updated successfully, but these errors were encountered:
Summary
Sometimes a consumer app might have a need to import all of the Sass variables and mixins available in the library at once, with no CSS build artifacts (such as classes or CSS variables) actually appearing.
This might be useful if you want to build a Veera-based component that the CVI library doesn't currently offer.
Having a single import for Sass entities will provide an easier upgrade path for consumer apps (internal paths of Sass files could be changed freely then).
What alternatives have you tried?
Right now it is impossible, you can only import both generated CSS and Sass artifacts mixed together or you can import Sass files one by one, which might be time-consuming and prone to breaking when upgrading a version of the library.
Does this feature request involve any updates to the reference design?
No
Implementation details
It should suffice to move imports for all Sass variables and mixins into one importable Sass file. We also would likely need to split files like
colors.scss
into a file with Sass data and another file dealing with the generation of CSS variables based on that data.The text was updated successfully, but these errors were encountered: