search

CottageLabs / edges

Data query, manipulation, search and visualisation front-end library
MIT License
8 stars 7 forks source link

Solve the CSS class portability problem #43

Open richard-jones opened 3 months ago

richard-jones commented 3 months ago

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 commented 3 months ago

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