`Value.Convert` to a `Union` no longer checks destination type validity about typebox HOT 2 CLOSED

@colatkinson Hi, thanks for reporting.

Yes, this looks like an oversight to me. The updates to Convert were intended to resolve a union/intersect (or distributive type) conversion issue that was submitted on #787. However the Union implementation was updated inline with the Intersect which applied a "best guess" conversion where it probably shouldn't have.

The update omitted the test for the "best possible" conversion (and early return) with the update attempting to rely a bit too much on the potential for Convert to return invalid values. I did mean to review this before publishing, but the update went through with some other changes on 0.32.16. Apologies.

I've published an update on 0.32.19 which reverts the Union logic specifically but retains the other conversion logic for 0.32.16. If you want to grab the latest off NPM and test things out your side, can close up this issue.

Cheers!
S

from typebox.

Pulled the latest and it works like a charm. Thanks for the fast response! I'll close this out.

from typebox.