-
Notifications
You must be signed in to change notification settings - Fork 105
GCI3 [Team LESS][2025] - Add Js rule #403
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
base: main
Are you sure you want to change the base?
Conversation
|
|
||
| - Correction of various typos in rules documentations | ||
|
|
||
| ### Changed |
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.
Could you move the Changed title above, the "Correction of various typos..." was in Changed section
|
This PR has been automatically marked as stale because it has no activity for 60 days. |
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.
Hello 👋
Did you have any reference or blog article which validates the rule? I have made some tests using https://jsperf.app and the results are quite the same with both compliant/non-compliant solutions. This awesome v8 blog article (Chromium engine) also talks about loops and it kind of challenges the existance of this rule.
So I think we should discuss the relevance of the rule before integrating it into the rule specification repository.
|
This PR has been automatically marked as stale because it has no activity for 60 days. |
Add new JS rule GCI3