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

Search box to find a specific API #2752

Closed
4 tasks
Nazarah opened this issue Jul 17, 2017 · 3 comments
Closed
4 tasks

Search box to find a specific API #2752

Nazarah opened this issue Jul 17, 2017 · 3 comments

Comments

@Nazarah
Copy link
Contributor

Nazarah commented Jul 17, 2017

Description

User should be able to look for a particular API in Dashboard rather than browsing the entire list.

User Story

"As an API owner, I want to have search option on Dashboard view, so that I can look for a particular API"

Definition of Done

  • User should be able to type name of an API to make it appear on Dashboard.
  • On typing the search string, matching result should be automatically populated in the dashboard
  • No of returned item in search result should be displayed
  • "No APIs found" text should appear if search result returns nothing.
    Open question: In case of a single result, should we show detailed view in the same page? (ref: Show Additional Details in Dashboard in case User has only one API #2753)

Wireframes

image

Alternet Approach: Is it possible to make the search option on Topbar contextual? So that when the view is in Dashboard, the search looks out for APIs in the Dashboard page, not the entire website.

@marla-singer
Copy link
Contributor

User should be able to type name of an API to make it appear on Dashboard.

What about searching for a proxy_backend path or api path?

@marla-singer
Copy link
Contributor

marla-singer commented Jul 28, 2017

On typing the search string, matching result should be automatically populated in the dashboard

This step would will be a little painful 🤔

@Nazarah
Copy link
Contributor Author

Nazarah commented Aug 1, 2017

@marla-singer

What about searching for a proxy_backend path or api path?

Lets start with simple search by API names. If it is feasible to implement this feature and we have usecase for it, we can always implement this later on.

This step would will be a little painful

what about lazy loading? My main concern is that user needs to press enter, wait for the page to reload with the found result. If it is too much work, save it for later implementation.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants