Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Showing content from https://github.com/typescript-eslint/typescript-eslint/issues/5845 below:

Explain situation around no-unsafe-* rules triggering on file changes in editors · Issue #5845 · typescript-eslint/typescript-eslint · GitHub

• I have looked for existing open or closed documentation requests that match my proposal.
• I have read the FAQ and my problem is not listed.

A lot of users have reported issues like this one: https://twitter.com/TkDodo/status/1582335847017242625

Every time I change something in my @trpcio router, @tseslint starts to complain on the usage sides in my editor (@intellijidea):

"Unsafe member access on an any value.(no-unsafe-member-access)"

Disabling and re-enabling eslint solves this. Any ideas what that could be?

I've personally felt this in VS Code a lot.

We should document this in our FAQs for when it happens to users:

• That the current / bandaid solution is to restart your ESLint server (along with how)
• What the structural underpinnings are (with links to pending issues)

https://typescript-eslint.io/docs/linting/troubleshooting

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4