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
Add at-mixin-no-risky-nesting-selector rule. #985
Add at-mixin-no-risky-nesting-selector rule. #985
Conversation
e30d734
to
3a34968
Compare
3a34968
to
c3ee96c
Compare
b856462
to
a834cb4
Compare
a834cb4
to
0ca7400
Compare
Thanks! I'll need to review this, but after a quick look I noticed that the rule name starts with |
@kristerkari Any thoughts on this? :) |
@pamelalozano16 I had a quick glance, at it looks good, but I would still like to properly read through the changes. I should have some time tomorrow to sit down and do some PR reviewing 👍 |
@pamelalozano16 also, did you notice my comment about the rule name ( |
1ec3c7c
to
903e7d0
Compare
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.
Still one comment about the rule name since I'm trying to keep the rule names consistent.
It seems like the most of the rules that start with the no-
prefix are ending in a plural form (no-dollar-variables
, no-duplicate-mixins
, no-global-function-names
, etc.).
The rules that start with something else seem to be mostly ending in a singular word. In this case it would mean that -selectors
could be changed to selector
.
Another thing is related to the naming of &
. There is already a rule called selector-no-redundant-nesting-selector
. I'm not sure what is the term that Sass uses, but it might be beneficial to keep it consistent unless using nesting-selector
makes the name unclear.
This would mean that the name would be at-mixing-no-risky-nesting-selector
. What do you think, would that name work?
src/rules/at-mixin-no-risky-parent-selectors/__tests__/index.js
Outdated
Show resolved
Hide resolved
Yes! Did you mean |
9c00f4d
to
5b83763
Compare
5b83763
to
3ca370b
Compare
Yeah! Sorry, I had a typo in the name. |
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.
Looks good now 👍
A link to this rule missing in the repo README, but I can add that after merging. |
Fix #892.