-
-
Notifications
You must be signed in to change notification settings - Fork 88
Fix Discriminator with Inline Bundling #436
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix Discriminator with Inline Bundling #436
Conversation
- Fix inline bundling: preserve discriminator-referenced schemas as components instead of inlining them - Fix composed bundling: properly resolve discriminator mappings to full component paths - Add comprehensive tests to validate discriminator mapping preservation - Prevents invalid bundled specs with broken discriminator references
Fix Bundling with Discriminator Mapping Additional test with non existent discriminator Fix Windows File Handles Remove unrealistic conditions Re-Add Comment Add space Test last case Remove test logging Fix Fix last test Checkpoint Start from failure Fix Discriminator with Inline Bundling
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #436 +/- ##
=======================================
Coverage 99.63% 99.64%
=======================================
Files 169 169
Lines 22893 22962 +69
=======================================
+ Hits 22809 22880 +71
+ Misses 79 77 -2
Partials 5 5
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
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.
LGTM! Thank you for the upgrade,
I've closed my previous PR and decided to work on each issue piecemeal.
Inline Bundling Changes
oneOf
oranyOf
for any ref, if it contains a discriminator mappingCons: Changes the behavior for the digital ocean spec, which is unfortunate since it's sort of the benchmark. But also I don't think it was working 100% correctly before