You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I need a possibility to filter swagger UI spec by tags. Unfortunately, current version of swagger-ui-react doesn't support filter property, which is implemented in the swagger-ui. That's why I can't enable it in my react component.
Describe the solution you'd like
We need to add filter prop to swagger-ui-react. It will be passed like every other prop and will be applied once, on mount.
I can prepare a PR that will solve the current issue.
I have prepared the PR, but I can't push it because of the permissions.
Describe alternatives you've considered
I was looking into writing a plugin to solve filtering needs. I think it wasn't the best idea due to the fact, that filter functionality is already written in swagger-ui. I believe that everyone will be happy to use filter functionality of the swagger-ui-react.
The text was updated successfully, but these errors were encountered:
Content & configuration
"swagger-ui-react": "^3.52.3"
Is your feature request related to a problem?
I need a possibility to filter swagger UI spec by tags. Unfortunately, current version of
swagger-ui-react
doesn't support filter property, which is implemented in theswagger-ui
. That's why I can't enable it in my react component.Describe the solution you'd like
We need to add
filter
prop toswagger-ui-react
. It will be passed like every other prop and will be applied once, on mount.I can prepare a PR that will solve the current issue.
I have prepared the PR, but I can't push it because of the permissions.
Describe alternatives you've considered
I was looking into writing a plugin to solve filtering needs. I think it wasn't the best idea due to the fact, that filter functionality is already written in
swagger-ui
. I believe that everyone will be happy to usefilter
functionality of theswagger-ui-react
.The text was updated successfully, but these errors were encountered: