-
Notifications
You must be signed in to change notification settings - Fork 12.5k
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
Fix tuple name homogeneity check #40118
Fix tuple name homogeneity check #40118
Conversation
what is the bug? From the tests it looks like the error didn't get reported on trailing (or final) named members in a previously-unnamed set of members. |
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.
Reading the code, it looks like that was exactly the bug.
@typescript-bot cherry-pick this into release-4.0 |
Heya @weswigham, I've started to run the task to cherry-pick this into |
Component commits: e1f4f9c Fix tuple name homogeneity check
Hey @weswigham, I've opened #40134 for you. |
Component commits: e1f4f9c Fix tuple name homogeneity check Co-authored-by: Wesley Wigham <t-weswig@microsoft.com>
Fixes a bug reported on the
babel
repo that I'd forgotten about until I read the release blog post.