-
-
Notifications
You must be signed in to change notification settings - Fork 9
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
v6: undefined
Added to Record Type
#459
Labels
Status: Released
It's now live.
Type: Bug
Inconsistencies or issues which will cause a problem for users or implementors.
Comments
joealden
added
Status: Triage
This issue needs to be triaged.
Type: Bug
Inconsistencies or issues which will cause a problem for users or implementors.
labels
May 19, 2024
RebeccaStevens
added a commit
that referenced
this issue
May 20, 2024
RebeccaStevens
added a commit
that referenced
this issue
May 20, 2024
RebeccaStevens
added a commit
that referenced
this issue
May 20, 2024
github-actions bot
pushed a commit
that referenced
this issue
May 20, 2024
## [6.0.1](v6.0.0...v6.0.1) (2024-05-20) ### Bug Fixes * type when merging index signatures ([5e8b9b6](5e8b9b6)), closes [#459](#459)
🎉 This issue has been resolved in version 6.0.1 🎉 The release is available on: Your semantic-release bot 📦🚀 |
This was referenced May 20, 2024
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Status: Released
It's now live.
Type: Bug
Inconsistencies or issues which will cause a problem for users or implementors.
Bug Report
When upgrading from
5.1.0
to6.0.0
, merging two records that both have types ofRecord<string, string>
results in a type of{ [x: string]: string | undefined; }
, when I'd expect it to be{ [x: string]: string; }
.EDIT: I understand that
Record<string, string>
isn't actually accurate for a concrete object that isn't proxied (as any properties not defined won't actually exist, so will beundefined
), but iffoo
andbar
have that type, I'd expect it to be respected (like it is in5.1.0
).Expected behavior
Actual behavior
The text was updated successfully, but these errors were encountered: