-
Notifications
You must be signed in to change notification settings - Fork 9k
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
Multi-selection in query parameter 'allowableValues' listbox for 'array' param type. #414
Conversation
based on our discussion in swagger-core, does this still apply? |
Brings backward compatibility for the 'allowMultiple' attribute.
Hi, |
@fehguy: what is your opinion? At least swagger-jaxrs users won't experience the list multiselect feature without this fix. |
Looks good, thanks for submitting |
Multi-selection in query parameter 'allowableValues' listbox for 'array' param type.
Note, there was also a bug in swagger-core that affects the generation of the drop-down, see swagger-api/swagger-core#483 |
So it seems that was a root cause of the issue. Nevertheless, I prefer current state of the art, because it's now enough to declare the jaxrs resource method query param as an array or List of enum type and you have a multiselectable list out of the box without a superfluous 'allowMultiple' attr. |
Brings backward compatibility for the 'allowMultiple' attribute.
Brings backward compatibility for the 'allowMultiple' attribute.
Multi-selection in query parameter 'allowableValues' listbox for 'array' param type.
Brings backward compatibility for the 'allowMultiple' attribute.
Updates the #304 behaviour - now it checks the 'array' param type instead of 'allowMultiple' attribute.
Partly adresses also the #118. It's also associated with swagger-api/swagger-js#83, but can live without it, though.
I haven't attached the generated swagger-ui.js to the pull request.