Skip to content

JSON IR for icss #7

@DanielHeath

Description

@DanielHeath

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions