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
Some of this can be externalized by adding bits of it to @import :
@import "my-component.css" layer(components);
But this isn't always possible or good practice for maintainable code.
Often the reason for wrapping code in an at-rule is tightly coupled with the code that is wrapped.
Using nesting is a choice and authors can choose not to nest.
@when does not help here because it wasn't designed for @layer, @scope, @container, ...
Personally I don't think @when should be shipped at all because it doesn't solve the issue fully. Maybe I am wrong here and @when could be used for all at rules?
The underlying issue is that at-rules can only be "combined" or "stacked" by nesting them. With the introduction of new at-rules and nested CSS source code will only become more heavily nested and less readable.
I don't have a concreet proposal for a syntax that could help here.
I do however think it is something that should be explored.
The text was updated successfully, but these errors were encountered:
Example :
This is starting to look a bit like the callback hell from JS :
Some of this can be externalized by adding bits of it to
@import
:@import "my-component.css" layer(components);
But this isn't always possible or good practice for maintainable code.
Often the reason for wrapping code in an
at-rule
is tightly coupled with the code that is wrapped.Using nesting is a choice and authors can choose not to nest.
@when
does not help here because it wasn't designed for@layer
,@scope
,@container
, ...Personally I don't think
@when
should be shipped at all because it doesn't solve the issue fully. Maybe I am wrong here and@when
could be used for all at rules?The underlying issue is that
at-rules
can only be "combined" or "stacked" by nesting them. With the introduction of newat-rules
and nested CSS source code will only become more heavily nested and less readable.I don't have a concreet proposal for a syntax that could help here.
I do however think it is something that should be explored.
The text was updated successfully, but these errors were encountered: