☂️ Rome classic lint rules, with scoping

[ematipico]

Note

This rules should be implemented once #2488 is closed.

This is because in order to correctly implement the rule, there's need to have access to the scope.

If you want to contribute

1. make sure you understand the requirements of the rule you would like to implement;
2. comment on this very issue telling saying which rule you would like to implement;
3. create a new task issue and link to this very umbrella issue (a member of the team will eventually assign it to you);
4. open a PR;

Note: please make sure to comment the issue saying which rule you'd like to implement, this would allow better coordination between contributors. Failing to do so would penalize yourselves against contributors that had followed these simple guildelines

Note: follow the naming convention guidelines: https://github.com/rome/tools/blob/archived-js/CONTRIBUTING.md#naming-patterns

List of rules that might require scoping resolution

• useCamelCase #2903
• noUnusedVariables: https://github.com/rome/tools/blob/archived-js/website/src/docs/lint/rules/js/noUnusedVariables.md
• noArrayIndexKey #3292
• noChildrenProp #3267
• noDangerouslySetInnerHtml #3204
• noDangerWithChildren #3313
• noRedundantShouldComponentUpdate: https://github.com/rome/tools/blob/archived-js/website/src/docs/lint/rules/react`/noRedundantShouldComponentUpdate.md Deprecated
• noRenderReturnValue #3248
• noUselessFragments #3254
• noVoidElementsWithChildren #3272
• useButtonType #3233
• useFragmentSyntax #3278
• useInterfaces: https://github.com/rome/tools/blob/archived-js/website/src/docs/lint/rules/ts/useInterfaces.md
  This rule was removed from Rome classic. We should consider it with care too pedantic, not needed
• noArguments: feature(rome_js_analyzer): semantic rules and "no arguments" lint rule #2807
• 📎 noCatchAssign #2848
• noFunctionAssign #2878
• noImportAssign: https://github.com/rome/tools/blob/archived-js/website/src/docs/lint/rules/js/noImportAssign.md
• noLabelVar #2837
• noRestrictedGlobals #3341
• useSimplifiedBooleanExpression #3338
• noShadowRestrictedNames #2897
• noShoutyConstants #2836
• noUndeclaredVariables #3281
• noFindDOMNode: https://github.com/rome/tools/blob/archived-js/website/src/docs/lint/rules/react/noFindDOMNode.md

Note: this rule requires access to the filename, which is not implemented yet

• useDefaultExportBasename
  Enforce the name of the file and the name of the default function / class export matches
• noSingleCharRegexAlternatives #2754 (requires parsing of regex)
• useTsExpectErrorPrefer #2753

  At the moment the linter lacks two capabilities requires to implement this, the first and most important is the ability for lint rules (and visitors) to inspect syntax tokens (currently lint rules can only query AST nodes), while a secondary one would be to allow rules to be enabled or disabled on a per-language basis: currently the existing JSX and TS rules are enabled all the time which isn't really a problem since they only query node for their language and thus never match in incompatible files, but if this rule needs to inspect all tokens we would want it to be disabled on non-TS files.

• useSortedSpecifiers #2755 (might be implemented in the formatter)

[Conaclos]

Some links are dead.

[ematipico]

Some links are dead.

Thank you! They should be fixed now

[IWANABETHATGUY]

@ematipico would you mind assigning me the task noCatchAssign? The related issue is here #2848

[IWANABETHATGUY]

@ematipico , would you mind assigning me the task noImportAssign? Related issue #2923

[IWANABETHATGUY]

noImportAssign is already merged.

[ematipico]

I will work on useButtonType

[ematipico]

The rule noFindDOMNode was mainly a warning of using an API meant to be deprecated. The API is now deprecated, so maybe we don't need this rule anymore