Allow to filter/select operations when adding a new API from a OpenAPI spec
Currently, if you need to create/update an API from an OpenAPI spec with only a small subset of the whole list of operations supported by your backend, you will need to edit the generated spec to remove all the operations/types not required which is boring and error prone, or import all of them and remove all the undesired ones one-by-one, which makes our lives sad and miserable..
A simple UI which allows to filter/select the specific operations we need to import/update would be awesome!!
Thank you for the feedback! We added this suggestion to the backlog and will update the item when we prioritize it for implementation.
Miserable is an understatement. Come on Azure. Open up a repo and have 17yo code the UI as a school project