types: only apply BufferToBinary if type strictly equals Buffer | null | undefined #15072
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fix #15057
Summary
The issue in #15057 is that BufferToBinary adds
Binary
to any type thatextends undefined
orextends null
, which is not intentional. This PR now only applies the BufferToBinary transform if the type strictly equals Buffer | null | undefined. I also made a similar change to other transforms we use for calculating the JSON serialized type.Examples