-
-
Notifications
You must be signed in to change notification settings - Fork 79k
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
Refactored and renamed grid mixins #12412
Conversation
I'm assuming that this doesn't change the generated CSS whatsoever? |
Yes, it doesn't change the generated CSS. |
Nope, fine as-is. |
I've been trying to tweak the mixing and agree that some of them have really tricky names. (for example the one you mentioned is in fact using the iteration pattern in LESS to create a loop but it's not very clear to an untrained eye and takes some practice to get it. Better naming helps readability while having no negative effect on the output size. |
@cvrebert Is this a backward compatible change? Renaming mixins seems iffy. |
FWIW, these seem fairly internal to me and I believe they're undocumented. |
Feel that. I'm definitely open to it given how complex those mixins are to begin with. |
Hmm, merging
|
Also, that's a JS minification error, but this PR only changes the Less/CSS. |
Yeah, super strange. I only see it with this PR—just tried again today. |
@mdo I can't repro. Builds fine locally. Try nuking |
Okay, so the problem was there was a merge conflict in the |
Weird problem with JS minification, but I'm happy it could be fixed. |
I don't know if this pull request is welcome, but I've refactored and renamed some grid mixins.
I think they are more descriptive (e.g.
.loop-grid-columns
is much clearer as.make-grid
in my opinion). And I also DRY'ed up the generation of screen size dependend grids (xs, sm, md, lg) with a new mixin.