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

[Feature]: Improve the UX with datasources when editing an API #12146

Open
1 task done
nayan-rafiq opened this issue Mar 22, 2022 · 2 comments
Open
1 task done

[Feature]: Improve the UX with datasources when editing an API #12146

nayan-rafiq opened this issue Mar 22, 2022 · 2 comments
Assignees
Labels
Enhancement New feature or request Frontend This label marks the issue or pull request to reference client code Integrations Product Issues related to a specific integration Query & JS Pod Issues related to the query & JS Pod Ready for design this issue is ready for design: it contains clear problem statements and other required information REST API plugin REST API plugin related issues

Comments

@nayan-rafiq
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Summary

When I'm on the API editor page, list of datasources and connections are shown on right.
It's not clear what I need to do with these two lists. If I click on a datasource from the list, a green label appears saying "In use". It also changes the base URL I was working on and there is no way to undo this.

Here are couple of things that can be improved.

  1. Do not show connections for API's.
  2. Save as Datasource button beside the URL input field can be displayed on top of the datasources shown on right.
  3. When user clicks on a datasource, rather than instantly adding the API to that datasource we can show a second form where user should be informed about the changes that's going to happen.
  4. There should be a link to a documentation on "What is a datasource" so that user can get more context if they want

Screenshot 2022-03-22 at 9 18 37 PM

Why should this be worked on?

This will make the UI more user friendly.

@Nikhil-Nandagopal
Copy link
Contributor

@nayan-rafiq thanks for the inputs!

@github-actions github-actions bot added Query & JS Pod Issues related to the query & JS Pod Actions Pod labels Mar 22, 2022
@rohan-arthur rohan-arthur added the Ready for design this issue is ready for design: it contains clear problem statements and other required information label Mar 24, 2022
@rohan-arthur
Copy link
Contributor

@nayan-rafiq thanks for the feedback, and while I agree the information that is shown in the right pane is confusing and vague. However, if I select one of the other datasources and like you said the base url gets changed, I can still hit cmd+z to undo this operation. Was this not apparent enough to you?

that vague pane itself: we will work on it

@Nikhil-Nandagopal Nikhil-Nandagopal added REST API plugin REST API plugin related issues and removed API pane labels Sep 12, 2022
@github-actions github-actions bot added Integrations Product Issues related to a specific integration and removed Query & JS Pod Issues related to the query & JS Pod labels Sep 12, 2022
@AmanAgarwal041 AmanAgarwal041 added the Frontend This label marks the issue or pull request to reference client code label Apr 19, 2023
@github-actions github-actions bot added the Query & JS Pod Issues related to the query & JS Pod label Apr 19, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Enhancement New feature or request Frontend This label marks the issue or pull request to reference client code Integrations Product Issues related to a specific integration Query & JS Pod Issues related to the query & JS Pod Ready for design this issue is ready for design: it contains clear problem statements and other required information REST API plugin REST API plugin related issues
Projects
None yet
Development

No branches or pull requests

6 participants