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
The infer from usage codefix only triggers from noImplicitAny errors, which are only available with noImplicitAny on. In particular, this makes it a lot less likely that JS users will use the codefix after #27610 is merged. Instead, noImplicitAny errors should be suggestions, which can trigger.
Use Cases
functionf(x){returnx+1}// in JS, the codefix should produce this:/** * @param {number} x */functionf(x){returnx+1}
This suggestion has a couple of problems:
It would be difficult or at least slow to generate no-implicit-any errors without noImplicitAny: true, since the code paths are often quite different.
inferFromUsage is not quite mature enough to be suggested everywhere to everybody all the time.
I'm working on (2), and (1) might not actually be a problem. A prototype is probably a good next step.
The text was updated successfully, but these errors were encountered:
Search Terms
infer from usage suggestion
Suggestion
The infer from usage codefix only triggers from noImplicitAny errors, which are only available with noImplicitAny on. In particular, this makes it a lot less likely that JS users will use the codefix after #27610 is merged. Instead, noImplicitAny errors should be suggestions, which can trigger.
Use Cases
This suggestion has a couple of problems:
I'm working on (2), and (1) might not actually be a problem. A prototype is probably a good next step.
The text was updated successfully, but these errors were encountered: