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
It would be great to have a way to delineate the different CSS modules / blocks -- e.g. in my case I often use BEM, creating a new file for each Block, which has a comment at the top, something like:
Using something like this (if it's present) to determine where one module / block ends and another begins would be very useful, say, by using a different background colour for each different block / module.
This would make it much easy to visually find specificity problems for particular blocks / modules.
The text was updated successfully, but these errors were encountered:
That’s an interesting idea, I like it. It’s certainly not trivial to implement, and currently there are other things I have in mind I want to do before tackling other issues.
Also, and this doesn’t relate to your idea in particular, I think that the danger is great to overload a tool with lots and lots of features and at the end it’s a bit difficult to use and not intuitive anymore. Do you know, what I mean? One of my top priorities is to make the tool as easy to use as possible, while still offering useful features. That’s always a balancing act, of course.
But I leave this issue open of course and I will try coming back to it once I have more free time.
It would be great to have a way to delineate the different CSS modules / blocks -- e.g. in my case I often use BEM, creating a new file for each Block, which has a comment at the top, something like:
/*************************
MENU.CSS
*************************/
Using something like this (if it's present) to determine where one module / block ends and another begins would be very useful, say, by using a different background colour for each different block / module.
This would make it much easy to visually find specificity problems for particular blocks / modules.
The text was updated successfully, but these errors were encountered: