Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upGitHub is where the world builds software
Millions of developers and companies build, ship, and maintain their software on GitHub — the largest and most advanced development platform in the world.
`lost-flex-coontainer` needs nowrap option #390
Comments
|
This may have been a mistake on my part, feel free to close if it doesn't make sense. |
|
@fStop, is this still an issue. Adding more params is something that I'd like to avoid but I see the potential need here. Let me know. Thank! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is this a feature request or a bug report?
Feature request
What is the current behavior?
lost-flex-container: rowoutputs:What is the desired behavior?
It would be nice to be able to pass a
nowrapparameter in, like:lost-flex-container: row nowrap;, instead of having to manually override it.What's the motivation or use-case behind changing the behavior?
In order to get
nowrapyou have to override withflex-wrap: nowrap, which is easy enough. But if you have stylelint set up to order selectors alphabetically (team decision, not mine), it will bark at you, wanting theflex-wrap: nowrapdeclaration to come first, which will then be overridden by thelost-flex-columndeclaration.What version of LostGrid, browser and browser version are affected by this issue? Did this happen in previous versions?
Lost: 7.1.1
browser is not relevant in this case...