Skip to content
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

Confusing discriminator behaviour #2743

Open
hotrush opened this issue Nov 26, 2024 · 0 comments
Open

Confusing discriminator behaviour #2743

hotrush opened this issue Nov 26, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@hotrush
Copy link

hotrush commented Nov 26, 2024

Context

Would be good to get much more clear discriminator behaviour

Current Behavior

This issue #2190 says that schema name (or title, doesn't matter) used as options values in the dropdown, but it's confusing because:

  • user doesn't know what value for what field you need to send (discriminator field is not even highlighted or so)
  • what schema from oneOf list relates to what discriminator value
  • schema name/title is not always self-explanatory, it's not named like SchemaWhenField1HasValueOfFoo

Expected Behavior

  • dropdown should be located at the discriminator field level
  • dropdown values should contain keys from discriminator mapping (actual field values) (if provided of course)
@mnaumanali94 mnaumanali94 added the enhancement New feature or request label Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants