dareharu / shareable-configs Goto Github PK

Related docs:

• tsconfig#module
• tsconfig#moduleResolution
• handbook/esm-node

That is all in the title as I said. "require" and "import" fields that are exporting the actual configuration are in reversed order.

variable selectors like let, const, and even var in the top-level scope should be allow "StrictPascalCase" format that match modifiers: global and const and should be disallow "strictCamelCase" format.

Currently, we cannot use [Strict]PascalCase format that matches enumMember. @dareharu/eslint-config always enforces us to use PascalCase format.

We assume there is so awesome if we could be used this feature:

export const enum BrandingColor {
  Primary = 0x06d6a0,
  Secondary = 0xa08de9,
  Info = 0x608bda,
  Warn = 0xf1c40f,
  Danger = 0xe22b46
}

For example:

export function delegateTo(_: any): RedStoneConfig {
                        // ^ Parameter name `_` must match one of
                        //   the following formats: strictCamelCase
}

ESLint complains to us that the interface name must not start with an upper-cased alphabet. For example,

interface ConsumeRange {
  offset?: number
  take?: number
}

interface GetDocumentsOptions extends ConsumeRange {
  cache?: boolean
  exclude?: string[]
}

The ConsumeRange and GetDocumentsOptions interfaces are invalid since @dareharu/eslint-config enforces the rule that interface name must not match the RegExp: /^[A-Z]/u.

This behavior is invalid action so should be resolved as soon as possible.