I like 3L, but find it pretty aggressive in some ways.
Unfortunately 3Ls namespaces quite often collide with my own mixins and find myself looking for bugs unkowingly produced by 3L.
Example: your .hidden has !important which overwrote everything I did in combination with my own .hidden – of course I commented yours out when the project started. But one day the bower part inside of CodeKit thought it was a good idea to update everything and I ended up with a new version of 3L; of course all my commented things in the version were overwritten aswell.
long story short–
I love many parts of the library but would like to have more control over what gets imported and what not.
How about boolean vars for every component where I simply and quickly could select what I want and what not.
Or even cooler: parameters on the import? And if not possible a special mixin to load 3L?
That way 3L could update whenever it wants and I keep my setup as expected.
What do you think?
Are you interested in a modular 3L?
I like 3L, but find it pretty aggressive in some ways. Unfortunately 3Ls namespaces quite often collide with my own mixins and find myself looking for bugs unkowingly produced by 3L.
Example: your
.hiddenhas!importantwhich overwrote everything I did in combination with my own.hidden– of course I commented yours out when the project started. But one day the bower part inside of CodeKit thought it was a good idea to update everything and I ended up with a new version of 3L; of course all my commented things in the version were overwritten aswell.long story short– I love many parts of the library but would like to have more control over what gets imported and what not.
How about boolean vars for every component where I simply and quickly could select what I want and what not.
Or even cooler: parameters on the import? And if not possible a special mixin to load 3L? That way 3L could update whenever it wants and I keep my setup as expected.
What do you think? Are you interested in a modular 3L?