Open tkmct opened 2 years ago
to avoid naming collision of class names with library users' application, what about adding prefixes or suffixes to class names of nanoether components? ex) .button-outer -> .nanoether--button-outer
.button-outer
.nanoether--button-outer
I think this is a good idea. Wish there was a way to scope it better.
to avoid naming collision of class names with library users' application, what about adding prefixes or suffixes to class names of nanoether components? ex)
.button-outer
->.nanoether--button-outer