-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
use of discriminator field is broken #195
Comments
@andrewjtech123 discriminator is not broken in ReDoc. Your spec is invalid. You use
If you want to have Having top-level definition with name |
Hi @RomanGotsiy yes I would be very interested in the vendor extension. I was never happy with the way i "hacked" the spec to do this, so I'm not surprised that it stopped working. |
hay @RomanGotsiy is there a link or some info you can send me on this ? we have a public beta starting soon and I need to get the fix in |
Here is an example spec using this vendor extension: https://gist.github.com/a62b1dc9324b99a689c31c8411844d09#file-extendedDiscriminator-yaml Would be great If you manage to get guts out of it yourself. I am too busy today to document this detailed. |
@andrewjtech123 updated previous post with a correct link |
hey @andrewjtech123, did you manage to hack the spec as you needed using that vendor-extension ? |
hi @RomanGotsiy . I was able to play around with discriminator to get it to do something that works for now. latest version in the repo should have it. Thanks for checking in ! https://andrewjtech123.github.io/rebilly-validschema/ |
Great. I'm glad you managed to get that working. I've seen you published it as a public beta on Shopify docs 🎉 I will let you know once I'm done with documenting |
Hey @andrewjtech123, Hope it will be helpful: |
we have been using discriminator field to indicate custom vs. regular object (with different attributes and required fields depending on how discriminator is set (true or false). This functionality is now broken.
not possible to select true or false any longer from the dropdown.
The text was updated successfully, but these errors were encountered: