Preserve exact type matches in union conversion #1282
Merged
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.
Description
Fixes union type conversion issue where
Value.Parse()
unnecessarily converts values to the first matching type in a union, even when the input already matches one of the union types exactly.Problem
When using unions like
Type.Union([Type.String(), Type.Number()])
, numeric values were being converted to strings because the conversion logic would coerce to the first compatible type rather than preserving the original when it's already valid.Fixes #1281