Issues

• [X] I have checked existing issues and there are no issues with the same problem.

eslint-config-rimac Version You Are Using

26.0.1

Your Config

{
    "extends": [
        "@rimac-technology/eslint-config/core",
        "@rimac-technology/eslint-config/react"
    ],
    "parser": "@typescript-eslint/parser",
    "parserOptions": {
        "project": "./tsconfig.json"
    },
    "ignorePatterns": [
        "**/node_modules",
        "**/*.generated.ts",
        "**/*.json",
        "**/*.gql"
    ],
    "overrides": [
        {
            "files": [
                "**/cypress/**/*.{cy,cy.helper}.ts"
            ],
            "plugins": [
                "cypress"
            ],
            "rules": {
                "cypress/assertion-before-screenshot": "error",
                "cypress/no-assigning-return-values": "error",
                "cypress/no-async-tests": "error",
                "cypress/no-unnecessary-waiting": "error",
                "cypress/no-pause": "error",
                "promise/catch-or-return": "off",
                "promise/no-nesting": "off"
            }
        }
    ],
    "rules": {
        "etc/no-deprecated": [
            "error",
            {
                "ignored": {
                    "preProcessSnapshot": "name",
                    "postProcessSnapshot": "name",
                    "returnValue": "name"
                }
            }
        ]
    }
}

Steps to reproduce

• Add "noUncheckedIndexedAccess": true to your tsconfig.json file
• Get value by indexing an array or object
• Check for null or undefined with nullish coalescing operator ??

Expected behavior

No eslint errors

Actual behavior

Got no-unnecessary-condition error

but value can be undefined

Requirements

• [X] I have read and followed the instructions above and understand that my issue will be closed if I did not provide the required information.

There should be a small snippet of code that would be linted with all the rules activated.

If there are any issues with any of the rules, the lint should fail to report that rule XX can't be found or is invalid.

https://github.com/tunnckoCore/eslint-config-charlint/blob/master/test.js

• [x] https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/docs/rules/space-before-blocks.md
• [x] https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/docs/rules/no-useless-empty-export.md
• [x] https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/docs/rules/no-redundant-type-constituents.md
• [x] https://eslint.org/docs/rules/lines-between-class-members
• [x] https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/docs/rules/no-unnecessary-condition.md

prettier-plugin-packagejson or see if there are simmilar solutions with eslint

https://github.com/kellyselden/eslint-plugin-json-files#supported-rules

Currently, eslint reports an error if it('should bla bla line in tests exceeds the max-len of 120 characters. As there is no way to go around this in a clean way, max-len rule should skip checking the it('should bla bla lines.

If there is a it('should bla bla line in tests that exceeds the max-len of 120 chars, it should not be reported by eslint.

Currently, invalid-nullable-output-type rule forces you to use Type | null if the field is decorated with { nullable: true.

Sometimes using name?: Type | null is also required.

The rule should be adjusted to not error when using undefined

Given the following where we have a nullable field alongside with defaultValue, it should not force the field to be Type | null

@Field(() => String, {
    defaultValue: "asdf",
    nullable: true
})
public description: string

This will require writing the rule from scratch in https://bitbucket.org/rimacautomobili/eslint-plugin-rimac/src/master/