We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
To prevent any mixin collisions between extensions, we should recommend the use of Less namespaces, similar to how we handle initiali(s/z)ers in JS.
https://lesscss.org/features/#mixins-feature-namespaces
They're not that tricky to understand, thankfully, using an ID-based system.
My suggested syntax would be #vendor__package. I don't know how Less would handle slashes, etc.
#vendor__package
#davwheat__sidebar-nav-items { .my-cool-mixin() { color: red; } } button.davwheat_btn { #davwheat__sidebar-nav-items.my-cool-mixin(); }
Eventually, core should switch to something like #flarum__core.xxx(), or similar.
#flarum__core.xxx()
The text was updated successfully, but these errors were encountered:
No branches or pull requests
To prevent any mixin collisions between extensions, we should recommend the use of Less namespaces, similar to how we handle initiali(s/z)ers in JS.
https://lesscss.org/features/#mixins-feature-namespaces
They're not that tricky to understand, thankfully, using an ID-based system.
My suggested syntax would be
#vendor__package
. I don't know how Less would handle slashes, etc.Eventually, core should switch to something like
#flarum__core.xxx()
, or similar.The text was updated successfully, but these errors were encountered: