-
-
Notifications
You must be signed in to change notification settings - Fork 938
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
Bugfix/issue#3105 selector max id nested at statements #3113
Bugfix/issue#3105 selector max id nested at statements #3113
Conversation
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.
Few minor organizational moments.
Could you rebase your branch on master
, please? We found that some tests for selector-max-id weren't running and your fix might affect these tests because now they are running.
{ | ||
code: ".foo { @if ($p == 1) { #bar #baz {} } }", | ||
description: "@if statement: nested compound selector" | ||
}, |
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.
I think tests containing @if
should go to test
function with syntax: "scss"
.
message: messages.expected(".foo #bar #baz #foo", 2), | ||
line: 1, | ||
column: 24 | ||
}, |
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.
I think tests containing @if
should go to test
function with syntax: "scss"
.
@BenjaminWFox You should either merge changes from |
@Arcanemagus Hmm, I thought I rebased but I haven't dealt with upstream/forked repos before - I probably got confused trying to get the right updates from the right place. Should I just squash them then? And would that be with something like |
Actually as @hudochenkov just pointed out to me in a different PR, all PR's here are squashed so it's not a huge issue. For your own reference though: The simplest method is to make sure your local Alternatively you can also do |
Requested changes were made in 803c2f0
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.
LGTM 👍
• Tests pass locally for me ✅
• Squashing merge should work 🤞
#3105
I haven't done a lot of these (edits/PRs) so I'm not sure if I missed something, but I couldn't find a scenario in the tests where the the check for 'atrule' was useful. Everything seemed to work as I expected when I removed it.