You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* 📦️ update typescript-eslint and adjust config
We still use the ("legacy setup")[1] on purpose: we'll upgrade to a flat
config in a separate PR, when we upgrade ESLint.
[1]: https://typescript-eslint.io/getting-started/legacy-eslint-setup
Rule changes:
* @typescript-eslint/ban-types have been split in multiple rules, most
of them are enabled by default. The configuration we used has been
ported to @typescript-eslint/no-restricted-types
* no-throw-literal isn't needed anymore as the new rule
@typescript-eslint/only-throw-error is covering the same thing and
more.
* @typescript-eslint/no-var-requires was replaced with
@typescript-eslint/no-require-imports.
* @typescript-eslint/no-unused-experessions was turned on in the
recommended rules, but we have a few cases where we avoid using an
`if` like `foo && bar()` that raise that error, so I disabled the rule
for now.
* 🚨 fix lint issues related to typescript-eslint update
* The new @typescript-eslint/only-throw-error reports quite a few (valid)
cases where we don't throw errors. I ignored those as issues as this was
generally what we wanted.
* Some eslint-disable comments were not needed, so I removed them
* Optional properties and arguments that also accept `undefined` now
raise an error
* typescript-eslint is also better at finding unused variables in catch
clauses
* And other minor things...
* Turn on rule no-unused-expressions
* Update developer-extension/src/panel/components/tabs/infosTab.tsx
Co-authored-by: Thomas Lebeau <[email protected]>
---------
Co-authored-by: zcy <[email protected]>
Co-authored-by: Thomas Lebeau <[email protected]>
0 commit comments