-
Notifications
You must be signed in to change notification settings - Fork 788
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
Allow numbers in descendant-combined type selectors (fix #1836) #1837
Conversation
A reasonable test might be to have some CSS that we know should parse, and see if it parses without errors. |
@willmcgugan Is there a spot in the tests for that sort of thing right now? I went looking, wanting to fit this in, but couldn't obviously see anything. If not I'll kick some testing off based around this. |
Don't believe so. Worth adding I think. Just one big string with known rules and edge cases. |
Cool. Sounds worthwhile. Will do. |
Actually, on second look, it looks like |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other than the typo you can fix in a jiffy, looks good to me!
Co-authored-by: Rodrigo Girão Serrão <5621605+rodrigogiraoserrao@users.noreply.github.com>
Co-authored-by: Rodrigo Girão Serrão <5621605+rodrigogiraoserrao@users.noreply.github.com>
Co-authored-by: Rodrigo Girão Serrão <5621605+rodrigogiraoserrao@users.noreply.github.com>
This fixes #1836; it'll also help folk style a
Markdown
with a bit more specificity too.NOTE: Looks like we may need some tests around this sort of thing; I would have added one for this problem as part of this PR but it wasn't clear to me where in the tests it should go, or indeed if we have any around this right now. We may want to review this as part of this or as a followup.