Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Solve the CSS class portability problem #43

Open
richard-jones opened this issue May 13, 2024 · 1 comment
Open

Solve the CSS class portability problem #43

richard-jones opened this issue May 13, 2024 · 1 comment

Comments

@richard-jones
Copy link
Member

richard-jones commented May 13, 2024

How can we deal with the issue where the change of a css class name requires a new or modified renderer.

For example, it would be quite good to have edges-specific classes only in edges, and no framework classes (e.g. no bootstrap rows, cols, etc). And then for them to be mapped onto the framework classes in some other layer.

This allows us to remain independent of the style framework, and to help us avoid clashes between host system classes and edges layout (e.g. row is a heavily overloaded style name)

Does such a mechanism exist? Or what could we do?

@richard-jones
Copy link
Member Author

See https://github.com/dcastil/tailwind-merge for some possible approaches

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant