-
Notifications
You must be signed in to change notification settings - Fork 223
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Default namespace? #523
Comments
Hello! ⭐ Do you mind giving an example of how you use an exposed utility once imported? :) |
Not at all! Take a look! @use 'config';
@forward 'config';
@forward 'functions' with (
$my-base-url: config.$base-url,
$my-breakpoints: config.$breakpoints,
$my-font-weights: config.$font-weights,
$my-gutter: config.$gutter,
$my-palette: config.$palette,
);
@forward 'mixins'; I'm trying to start the discussion for the next version. Maybe I remember of another topics to address. |
Ops! I'm sorry. I misunderstood your question! I use them this way: .foo {
@include my.exposed-mixin('bar');
} |
Ah I see. I’m just remembering how this thing works. Wondering whether or not we should suggest a default namespace. I don’t dislike Maybe |
I chose I just wanted to feel how would be to code using the namespace idea on my styles. On the bright side, we can avoid collisions between local and global members, like |
I came to the conclusion that to use a namespace is absolutely necessary, to avoid making a mess with new CSS features, like |
I think I would be more in favour of smaller, more focused modules that are namespaced with a singular noun that logically identifies what the modules provides. For example, |
One topic per issue?
I've been using
my
on my tests:What do you think, @Elrendio || @KittyGiraudel ?
The text was updated successfully, but these errors were encountered: