Is there a correct way to handle typescript-eslint/no-unsafe-returns with async components? #11798
Unanswered
ayochim
asked this question in
Help/Questions
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
When attempting to load a few global components async during app startup,

typescript-eslint/no-unsafe-returns
is suddenly yelling at me. This only started happening recently, after upgrading a few eslint packages. Is there a way to make this scenario a "safe return"? Or should I resign to disabling this rule where I need to? See below.Here's the root cause feature if it's relevant
typescript-eslint/typescript-eslint#8693
Beta Was this translation helpful? Give feedback.
All reactions