-
Notifications
You must be signed in to change notification settings - Fork 12.6k
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
Always emit any
for get
accessors
#36279
Conversation
…ors in older TypeScript versions.
@typescript-bot cherry-pick this to release-3.7 |
Hey @DanielRosenwasser, I couldn't open a PR with the cherry-pick. (You can check the log here). You may need to squash and pick this PR into release-3.7 manually. |
Don't we normally elide the type annotation for |
Eeeyes? I think so. Unsure. @sandersn ? |
Correct, in #36216 it was reported that 3.6.x incorrectly thinks that an error under |
@rbuckton is right, we elide the type annotation for private declarations. The correct thing is not to error on then, so I don't think we should take this PR. |
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.
We should not error instead of emitting an any
type.
I'm potentially okay with that - can you check out #36280 then? |
Fixes at least half of #36216 by always emitting
any
forget
accessors.Note that
set
accessors stil emit without parameter types, and from what I can tell TypeScript 3.6 is okay with that undernoImplicitAny
.