-
-
Notifications
You must be signed in to change notification settings - Fork 161
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
nth-of-type support #192
Comments
👍🏻 |
Yeah I'd be interested in a PR for this. It'd need to be a global setting as well as on a per-element basis. |
Terrific, I'll put something together. |
+1 Just ran into this |
@zgreen Are you still up for working on a PR? (or maybe you already are) 😄 Any help would be epic! |
@zgreen I just noticed that you forked and had some work going already on this. Let me know if you need anything. |
Yeah, it's just about there—work got in the way. Got it working w/ |
Thanks! Don't worry about any sort of rush. Enjoy this last week before 2016. |
👍 |
It'd be really cool if all Lost's rules could accept values in any order. :^\ |
@corysimmons I'm looking into this, actually. I'm curious what it will take. Still really diving into the code right now to better understand it all as a whole. 😄 |
@corysimmons see #213 for follow up to your last comment. |
@peterramsing Feel free to ping me while you're diving into code for explanations about anything. Happy to help you wrap your head around my garbage code. :^) |
@corysimmons You bet! I plan to sift through all the code + tests (#208) tonight and though the weekend. I'll probably release a 6.6.3 release with the npm updates through the weekend and then pursue #195 to get another patch out before getting 6.7.x scoped and begin the roadmap to 7.0.0. I'll probably ping you throughout. 😄 |
Awesome, you're doing an amazing job! I'm so happy you took this project over. |
👍 |
It would be great if Lost supported
nth-of-type()
grid spans in addition to the currentnth-child()
implementation.Use case
Obviously, one can work around this by simply adding a wrapping element, but that solution may neither be semantic nor desired.
I'm happy to submit a PR, if you're interested. Thanks for all your work—this project is terrific.
The text was updated successfully, but these errors were encountered: