-
Notifications
You must be signed in to change notification settings - Fork 2
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
Consider namespacing variables #87
Comments
Did a quick review of Bootstrap, Semantic UI and Carbon Components - don't see any prefixing on their variables but I am seeing a naming pattern. We use patterning through our variables but we aren't being as consistent or purposeful about it as we could be. Here's the current state - Constant Variablespattern: Theme Variablespattern: Component Variablespattern: Instead of prefixing everything with Constant Variablespattern: Thoughts? |
True. But those are also established libraries... so they can get away with more stuff. I also don't like that they're not prefixed. If bootstrap's variables were prefixed, it would make our lives easier now during Willow dev, as we'd know what variables belong to them vs us :) You know me - I like namespaces. |
We can get away with whatever we want too! 😃 🎉 Previously prefixing to describe the variable ( I honestly don't feel strongly about it either way, but want more input from others and also want to prioritize this into the backlog...probably needs to make v1 since it's a big break for any of the existing 0.x.0 versions. @dbay24 @Keale2 @bollinghball @rebekahpadula @townivan @susannekappler |
I made branches with this change so we could see the idea in action |
SASS variables are global, so they are available to (and can be overwritten by) anything. Some of our variable names are very simple (such as $space) and there's a reasonable chance of a collision with another library/the user's own code.
We should consider namespacing all variables with a
$willow-
prefix. This will greatly reduce the chances of a collision.The text was updated successfully, but these errors were encountered: