-
-
Notifications
You must be signed in to change notification settings - Fork 6.5k
[Feature]: support type inference for function parameters #15034
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
This issue is stale because it has been open 30 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
PR very much welcome - as noted in #13339 there are some regression tests added, so hopefully we won't have the same problems. |
…ctions (jestjs#15034) WIP will be amended
…ctions (jestjs#15034) WIP will be amended
…ctions (jestjs#15034) WIP will be amended
…ctions (jestjs#15034) WIP will be amended
@SimenB Hey :) I started working on a PR in draft mode. Before completing it, I wanted to know if that's the right direction. I also had two specific questions about the PR:
These failures seems to me like the expected behavior of this new feature, meaning that it's likely to introduce breaking changes to existing code. What are your thoughts on this? |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
🚀 Feature Proposal
This is identical to #13267, which was implemented in https://github.com/jestjs/jest/releases/tag/v29.1.0 (#13268), but was soon reverted in https://github.com/jestjs/jest/releases/tag/v29.1.2.
So in fact, the feature remains unimplemented.
Motivation
Faster detection of broken function signatures + allow IDEs to auto rename the test parameters when renaming the original function parameters.
Example
No response
Pitch
Seeing that this feature request was opened here in the past, I assume it fits here still.
The text was updated successfully, but these errors were encountered: