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
In order to make icss implementations reusable in a variety of languages and environments, it is desirable to have a standard way to store the mapping between logical and generated class names.
The obvious (to me) way would be to store <filename>.icss.json containing e.g.
If the canonical implementations such as css-modules implemented something like this, it would become really easy to consume CSS modules from non-javascript projects.
The text was updated successfully, but these errors were encountered:
In order to make icss implementations reusable in a variety of languages and environments, it is desirable to have a standard way to store the mapping between logical and generated class names.
The obvious (to me) way would be to store
<filename>.icss.json
containing e.g.{"button": "CONTACT__button__Xv7f2 CORE__typography-v8s8fj"}
Although I could be persuaded that it should instead be
{"button": ["CONTACT__button__Xv7f2", "CORE__typography-v8s8fj"]}
If the canonical implementations such as css-modules implemented something like this, it would become really easy to consume CSS modules from non-javascript projects.
The text was updated successfully, but these errors were encountered: