Skip to content

Conversation

@ShreyaThapa
Copy link
Contributor

After adding partial discriminators and testing with the TS SDK, I discovered a problem. Making this update gets rid of the problem. I have also tested this change with the TS SDK, it can now match on all customer schemas with their new change with smart union support.

The problem:

  • When a discriminator exists, code generators (including Speakeasy) use it as the source of truth
  • Schemas in oneOf but not in the discriminator mapping are effectively ignored (business vcrs in our case)

Our option:

  • Remove the discriminator entirely - Let Speakeasy handle it purely with populated-fields.

@ShreyaThapa ShreyaThapa merged commit a759de3 into main Nov 20, 2025
5 checks passed
@ShreyaThapa ShreyaThapa deleted the fix/discriminators branch November 20, 2025 15:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants