| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
| "@typescript-eslint/no-namespace": "off", | ||
| "@typescript-eslint/no-non-null-asserted-optional-chain": "off", | ||
| "@typescript-eslint/no-var-requires": "off", | ||
| "@typescript-eslint/no-empty-interface": "off", |
There was a problem hiding this comment.
This one deserves an explanation; while it's definitely bad to have empty interfaces, we seem to have quite a few cases which are "valid" in that they do things like rebinding another interface with new type variables (many in types), providing an interface that is augmented elsewhere (SourceFile), and so on.
Sorry, something went wrong.
|
After #55137, I've also added no-extra-boolean-cast, which similarly is too strict to work. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Follow-up to #54693.
This PR triages the rules that should "obviously" be disabled or fixed.
This caught a case where I had not noticed a stray debugger line in a PR.