-
Notifications
You must be signed in to change notification settings - Fork 97
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
Consider the use of sass modules in at-each-key-value-single-line rule #580
Consider the use of sass modules in at-each-key-value-single-line rule #580
Conversation
Thanks! I'll try to review asap |
This should support cases where the module is imported with a different namespace than the default |
Namespace support added. Thanks for your advice. |
@jhae-de great job with adding so many test cases! I still need to go through the changes more in detail before I can approve. |
Thank you for your review @stof. I added more test cases and hopefully solved all problems. |
The `moduleNamespace` function now returns - `null` if the namespace is removed with `as *` - the custom namespace if it is set with `as ...` - the default namespace in all other cases
I see that @stof has done a great job with the review here, so I trust that he can also say if he thinks that this is good to be merged now :) At least there are a lot of test cases! |
@stof Could you please re-review this (as you have already reviewed the PR) to see if everything is ok now? I could release a new minor version with this and the other PRs. |
This was released in 4.1.0: |
The
at-each-key-value-single-line
rule does not report an error when set totrue
and using sass modules.This should fail but it doesn't:
This pull request changes the rule to take the use of sass modules into account.