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
Instead of generating hashes, how about keeping a global key map based on the prefix and just incrementing the number as needed e.g. Layout-typeContainer-1 and Layout-typeContainer-2?
As I understand it, we already must ensure that our prefix is unique otherwise we will overwrite other styles, or has this changed?
The text was updated successfully, but these errors were encountered:
I like the sheet-rule naming in dev (but kill the unique number if possible). I can also control it if I really want to (at least in my own code), but the descriptive nature is a plus.
just a hash in prod sounds fine to me.
While we are in this area, I find myself prefixing everything in our libraries just to be sure there is no conflict with material-ui. Any thoughts about plugging in a naming strategy for this or allowing prefix/suffix?
The hashes are quite long for class names and can really add up when inspecting elements to figure out adjustments.
For example - checkout the length of the layout (granted I have specified a lot of props):
Instead of generating hashes, how about keeping a global key map based on the prefix and just incrementing the number as needed e.g.
Layout-typeContainer-1
andLayout-typeContainer-2
?As I understand it, we already must ensure that our prefix is unique otherwise we will overwrite other styles, or has this changed?
The text was updated successfully, but these errors were encountered: