-
Notifications
You must be signed in to change notification settings - Fork 924
refactor(experimental): improve getTupleCodec type inferences #2344
Conversation
🦋 Changeset detectedLatest commit: 5cf4020 The changes in this PR will be included in the next version bump. This PR includes changesets to release 35 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
This stack of pull requests is managed by Graphite. Learn more about stacking. Join @lorisleiva and the rest of your teammates on Graphite |
248f04d
to
d116532
Compare
d116532
to
de73851
Compare
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.
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.
b8caa96
to
e6d76e0
Compare
de73851
to
87e679c
Compare
e6d76e0
to
d309da8
Compare
87e679c
to
84e4286
Compare
Merge activity
|
84e4286
to
5cf4020
Compare
🎉 This PR is included in version 1.91.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Because there has been no activity on this PR for 14 days since it was merged, it has been automatically locked. Please open a new issue if it requires a follow up. |
This PR follows the footsteps of #2181 which improved the type inferences of
getStructCodec
andgetDataEnumCodec
by inferring the types from the provided codecs instead of inferring the other way around.This PR does the same with the
getTupleCodec
and also makes use of theDrainOuterGeneric
helper from the previous PR to reduce the amount of instantiations TypeScript does when resolving the codec types.