Rule

@typescript-eslint/naming-conventions

Current Behavior

Yells when using numbers as prefixes in properties

Desired Behavior

Should be able to use numbers and numerically prefixed values

const sizes = {
	3xl: "2rem";
}

Can do this by adding:

      {
        "selector": "property",
        "format": null,
        "filter": {
          "regex": "^[0-9]+",
          "match": true
        }
      }

Configuration(s) Used

• default
• core
• typescript
• react
• format

Rule

@typescript-eslint/naming-convention

Current Behavior

Yells about import SwaggerParser from "@apidevtools/swagger-parser"

Desired Behavior

Allow me to import it in PascalCase

Configuration(s) Used

• default
• core
• typescript
• react
• format

We really should add a test directory that references this eslint configuration, validating that rule changes are actually being applied as we expect.

Rule

import/prefer-default-export

Current Behavior

Files with a single export error

VSCode Screenshot

Desired Behavior

We should generally prefer named exports in a file unless there are certain circumstances within a codebase (like next) where there are conventions for certain files.

Configuration(s) Used

• default
• core
• typescript
• react
• format

Rule

unicorn/filename-case

Current Behavior

Yells about kebab-casing filenames for *.tsx files (probably also *.jsx).

VSCode Screenshot

Desired Behavior

Enforces pascal-case for React files

Configuration(s) Used

• default
• core
• typescript
• react
• format

Rule

@typescript-eslint/no-magic-number

Current Behavior

Errors in enums, numeric literals, type indices, and read-only class properties.

Desired Behavior

Should not error for enums, numeric literals, or read-only class properties. Type indices should be configured as needed because changes to function signatures have a much higher potential to increase hard to discover flake

Configuration(s) Used

• default
• core
• typescript
• react
• format

Rule

unicorn/prevent-abbreviations

Current Behavior

Currently, the rule, when used with React, doesn't allow for the use of props in any form (see screenshot).

VSCode Screenshot

Desired Behavior

While props is technically an abbreviation, it is semantically appropriate within a React codebase.

Configuration(s) Used

• default
• core
• typescript
• react
• format