oursky / eslint-oursky Goto Github PK

DefinitelyTyped/DefinitelyTyped@8ce2499

https://eslint.org/docs/rules/eqeqeq#allow-null

I have trouble passing the lint test due to error when I nest a Text component inside another Text component:

<View>
  ...
  <Text style={styles.footnoteText}>
    {'*Only receipt scanning is available in the app.\n'}
    {'For other document types, please '}
    <Text style={styles.contactUsHyperlink} onPress={openURL}>
      {'contact us'}
    </Text>
    {'.'}
  </Text>
  ...
</View>

Error message:

error  Raw text (*Only receipt scanning is available in the app.) cannot be used outside of a <Text> tag  react-native/no-raw-text

Feel free to let your comments below

consistent-return requires default case even for exhaustive switch in TypeScript, undermining usefulness of @typescript-eslint/switch-exhaustiveness-check.

Example: https://typescript-eslint.io/play#ts=5.0.4&sourceType=module&code=FAFwngDgpgBAkgOwgVxDAvDA5AQyzAH2wCN8isBjLYYAM2QQpAEsB7BGEKAZxAApmSVAC54QkAEpRvAE6CA5jADewGGpjcA7sxAUAFjAHiJy1erUUc3WLiyiZUEMhkdcECABsoWANxnzltYkdjAOTi4kOAhReH7mFlY2VPaOzq6WIL7+MAC+wDlAA&eslintrc=N4KABGBECmAeAu0B2ATAzpAXGA2jNANgJZLyYBO0AxgPYC2dyK0KkANFAA4ECuA5iUwABeAE9O0NFXJFO8ALSTipAPSVaDJi0gBdNuCjkeBSVjCgIESLSRoiaRKXmV4PckjMxy5GuUgGAXxAAoA&tsconfig=N4KABGBEDGD2C2AHAlgGwKYCcDyiAuysAdgM6QBcYoEEkJemy0eAcgK6qoDCAFutAGsylBm3TgwAXxCSgA

ref: https://stackoverflow.com/questions/67638957/how-can-i-have-consistent-return-with-exhaustive-switch-case-statements

Prettier will remove parathesis so this rule will be violated.

https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/docs/rules/no-implicit-any-catch.md

I got these output when trying to use version 9.0.1:

can't resolve reference #/definitions/directiveConfigSchema from id #
can't resolve reference #/definitions/directiveConfigSchema from id #
can't resolve reference #/definitions/directiveConfigSchema from id #
can't resolve reference #/definitions/directiveConfigSchema from id #
can't resolve reference #/definitions/modifier from id #

Config:

module.exports = {
  root: true,
  plugins: ['@oursky'],
  parserOptions: {
    sourceType: 'module',
    project: './tsconfig.json',
  },
  extends: [
    'plugin:@oursky/typescript',
  ],
};

Seems related to typescript-eslint/typescript-eslint#5525

https://github.com/SonarSource/eslint-plugin-sonarjs/blob/master/docs/rules/cognitive-complexity.md

The new JSX transform is now widely supported. The best practice is not to import React into scope. Turn off the rules to promote best practice.

For example

<IconButton type="button" title="Sign out" ariaLabel="Sign out" />

With options

allowString: false
allowNumber: false
allowNullableObject: false
allowNullableBoolean: false
allowNullableString: false
allowNullableNumber: false
allowNullableEnum: false
allowAny: false
allowRuleToRunWithoutStrictNullChecksIKnowWhatIAmDoing: false

https://eslint.org/docs/rules/no-implicit-coercion

refs 7eb91d1

I tried to upgrade to 2.31.0, but still the same error. refs: https://github.com/oursky/eslint-oursky/runs/645269495

• @typescript-eslint/no-explicit-any
• @typescript-eslint/no-unsafe-member-access
• @typescript-eslint/no-unsafe-assignment
• @typescript-eslint/no-unsafe-return
• @typescript-eslint/no-unsafe-call
• @typescript-eslint/strict-boolean-expressions
• array-element-newline
• no-mixed-operators
• no-undefined
• Turn on option allowArgumentsExplicitlyTypedAsAny of @typescript-eslint/explicit-module-boundary-types

As type-checking is done by TypeScript itself, eslint shouldn't have no-undef rule for typescript files.

This will be an error as JSX is a global.

function SomeComp(): JSX.Element {
  // ...
}

Official ref: https://typescript-eslint.io/linting/troubleshooting#i-get-errors-from-the-no-undef-rule-about-global-variables-not-being-defined-even-though-there-are-no-typescript-errors

Please add the following to .gitignore:

.DS_Store
*.pem
*.cer
*.cert
*.p12
*.pfx
*.key
.env
docker-compose.override.yml