-
Notifications
You must be signed in to change notification settings - Fork 9
API Client Connector #43
Comments
Designs for issue found here: Please review! |
Thanks for sharing, SJ. A couple comments ... I thought we discussed providing a Swagger UI-like view of the resource paths and verbs instead of the traditional action list? If we go with a traditional action view, then we need to be prepared for:
I can't remember if we thought there was a need for action configuration for API connector. If so, we might need to discuss designs around that part as well. |
@kcbabo Thanks for the feedback! I will update the review page to reflect more of a swagger ui with resource paths as the categories and actions/verbs listed under, like so: That's what you're referring to correct? We would still want to possibly consider a large list. Perhaps just enable scrolling and utilize the filter tool we use throughout the app. As for configuration for actions, I had that in the original design but we discussed to remove that functionality for the time being and just list everything to serve more as a review step. No action needed for this step in the workflow. Since this step is more of a review, would we still need the ability to search/filter at this time? @dongniwang @amysueg thoughts? |
API client connectors will show up in first step of Create Connection flow as available connectors.
The text was updated successfully, but these errors were encountered: