Skip to content
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

chore: promote rules #532

Merged
merged 7 commits into from
Oct 16, 2023
Merged

chore: promote rules #532

merged 7 commits into from
Oct 16, 2023

Conversation

ematipico
Copy link
Member

Summary

Closes #410

Test Plan

CI should pass

@ematipico ematipico temporarily deployed to Website deployment October 16, 2023 10:32 — with GitHub Actions Inactive
@github-actions github-actions bot added A-Project Area: project A-Linter Area: linter A-Tooling Area: internal tools A-Website Area: website L-JavaScript Language: JavaScript and super languages A-Diagnostic Area: diagnostocis labels Oct 16, 2023
@ematipico ematipico requested review from Conaclos and a team October 16, 2023 10:32
@ematipico ematipico temporarily deployed to Website deployment October 16, 2023 10:38 — with GitHub Actions Inactive
@github-actions
Copy link
Contributor

Parser conformance results on

js/262

Test result main count This PR count Difference
Total 49701 49701 0
Passed 48642 48642 0
Failed 1059 1059 0
Panics 0 0 0
Coverage 97.87% 97.87% 0.00%

jsx/babel

Test result main count This PR count Difference
Total 40 40 0
Passed 37 37 0
Failed 3 3 0
Panics 0 0 0
Coverage 92.50% 92.50% 0.00%

symbols/microsoft

Test result main count This PR count Difference
Total 6322 6322 0
Passed 2036 2036 0
Failed 4286 4286 0
Panics 0 0 0
Coverage 32.20% 32.20% 0.00%

ts/babel

Test result main count This PR count Difference
Total 662 662 0
Passed 592 592 0
Failed 70 70 0
Panics 0 0 0
Coverage 89.43% 89.43% 0.00%

ts/microsoft

Test result main count This PR count Difference
Total 17646 17646 0
Passed 13454 13454 0
Failed 4190 4190 0
Panics 2 2 0
Coverage 76.24% 76.24% 0.00%

@ematipico ematipico temporarily deployed to Website deployment October 16, 2023 10:52 — with GitHub Actions Inactive
@github-actions github-actions bot added the A-CLI Area: CLI label Oct 16, 2023
@ematipico ematipico force-pushed the feat/rule-promotion branch from b37401a to 1638fd0 Compare October 16, 2023 11:11
@ematipico ematipico temporarily deployed to Website deployment October 16, 2023 11:11 — with GitHub Actions Inactive
Copy link
Member

@Conaclos Conaclos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good!

I think you forgot to promote noGlobalIsFinite to suspicious.

I could also rename noExcessiveComplexity to noExcessiveCognitiveComplexity.

Also we could promote and recommend noDuplicatePrivateClassMembers and noSuperWithoutExtends syntax rules?

@ematipico
Copy link
Member Author

Also we could promote and recommend noDuplicatePrivateClassMembers and noSuperWithoutExtends syntax rules?

These aren't lint rules, they are syntax rules. Users aren't able to configure them. They always run because they are meant to catch syntax errors or runtime errors.

@Conaclos
Copy link
Member

These aren't lint rules, they are syntax rules. Users aren't able to configure them. They always run because they are meant to catch syntax errors or runtime errors.

Is it normal the recommend flag is set to false and they are placed in a nursery folder?

@ematipico
Copy link
Member Author

Is it normal the recommend flag is set to false and they are placed in a nursery folder?

No, it seems that the script didn't work. Let me fix that, good catch

@ematipico ematipico force-pushed the feat/rule-promotion branch from f2b5495 to 8d945f7 Compare October 16, 2023 12:29
@ematipico ematipico requested a review from Conaclos October 16, 2023 12:29
@ematipico ematipico temporarily deployed to Website deployment October 16, 2023 12:29 — with GitHub Actions Inactive
Copy link
Member

@Conaclos Conaclos left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think you forgot to promote noGlobalIsFinite to suspicious.

I could also rename noExcessiveComplexity to noExcessiveCognitiveComplexity.

Also, a changelog entry is missing :)

@ematipico
Copy link
Member Author

Also, a changelog entry is missing :)

Any suggestion/help? I don't know what's the expected changelog line

@Conaclos
Copy link
Member

Any suggestion/help? I don't know what's the expected changelog line

We could use the same template that the previous version, creating a Promoted rules section.

@ematipico
Copy link
Member Author

Done!

@ematipico ematipico requested a review from Conaclos October 16, 2023 14:28
@github-actions github-actions bot added the A-Changelog Area: changelog label Oct 16, 2023
@ematipico ematipico force-pushed the feat/rule-promotion branch from 4fbbe70 to 2f4c7e3 Compare October 16, 2023 15:30
@ematipico ematipico temporarily deployed to Website deployment October 16, 2023 15:30 — with GitHub Actions Inactive
@ematipico ematipico force-pushed the feat/rule-promotion branch from 2f4c7e3 to b6e9d61 Compare October 16, 2023 15:47
@ematipico ematipico temporarily deployed to Website deployment October 16, 2023 15:47 — with GitHub Actions Inactive
@ematipico ematipico force-pushed the feat/rule-promotion branch from b6e9d61 to be64ce5 Compare October 16, 2023 16:08
@ematipico ematipico temporarily deployed to Website deployment October 16, 2023 16:08 — with GitHub Actions Inactive
@ematipico ematipico merged commit d432985 into main Oct 16, 2023
18 checks passed
@ematipico ematipico deleted the feat/rule-promotion branch October 16, 2023 17:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Changelog Area: changelog A-CLI Area: CLI A-Diagnostic Area: diagnostocis A-Linter Area: linter A-Project Area: project A-Tooling Area: internal tools A-Website Area: website L-JavaScript Language: JavaScript and super languages
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants