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
Right now some of the styles created specifically for Storybook are loaded even if a consumer app doesn't have anything to do with the CVI library Storybook.
There're not many styles there, but it could become a bigger problem with more Storybook customisations coming.
These two files in main.scss are the ones in question:
These imports should still load in the Storybook, but should not be present in main.scss.
What alternatives have you tried?
No response
Does this feature request involve any updates to the reference design?
No
Implementation details
It would be desirable to retain Sass as a CSS preprocessor when writing styles for Storybook. Maybe this integration could help: https://storybook.js.org/recipes/sass.
It might make sense to remove the CVI CSS variables from the Storybook styles and replace them with hardcoded styles or local CSS variables.
The text was updated successfully, but these errors were encountered:
Summary
Right now some of the styles created specifically for Storybook are loaded even if a consumer app doesn't have anything to do with the CVI library Storybook.
There're not many styles there, but it could become a bigger problem with more Storybook customisations coming.
These two files in
main.scss
are the ones in question:These imports should still load in the Storybook, but should not be present in
main.scss
.What alternatives have you tried?
No response
Does this feature request involve any updates to the reference design?
No
Implementation details
It would be desirable to retain Sass as a CSS preprocessor when writing styles for Storybook. Maybe this integration could help: https://storybook.js.org/recipes/sass.
It might make sense to remove the CVI CSS variables from the Storybook styles and replace them with hardcoded styles or local CSS variables.
The text was updated successfully, but these errors were encountered: