Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Prefer a likely literal over anonymous type in --noImplicitAny codefixes #36015
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Prefer a likely literal over anonymous type in --noImplicitAny codefixes #36015
Changes from all commits
ddd7f24
e33cc59
76fd88a
18fdff5
17fb22f
02c2426
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This looks like an unintended positive bug fix, right? Other places (e.g.
codeFixInferFromCallInAssignment
) inferany
for variable types that would otherwise be describable asunknown
.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure what you mean by "unintended positive".
void
was wrong andany
is right as far as I can tell.I think, in most positions, inferring
any
vsunknown
is a matter of preference -- how strict do you want the result to be? Right now I assume that people want pretty loose results, since I expect people will use this after converting from .js to .ts, and before trying to get rid of any explicitany
.We could discuss adding another fix to the codefix, one that defaults to
unknown
when possible. I think it would be a decent idea, but hard to explain in the space of a codefix title.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Oh yes I think we're on the same page - I meant that the change from
void
toany
is positive, and I didn't initially intend it as part of this PR's changes. 👍