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

Add Search box on the Dashboard page #3367

Merged
merged 4 commits into from Jan 31, 2018
Merged

Add Search box on the Dashboard page #3367

merged 4 commits into from Jan 31, 2018

Conversation

marla-singer
Copy link
Contributor

Changes

  • Add input
  • Display count of found result
  • Display No APIs found if it is

Closes #2752

Developer checklist

This checklist is to be completed by the PR developer:

  • Alternative solutions were compared/discussed before writing code
    • trade-offs with this solution are considered acceptable
  • Code in this PR adheres to the project styleguide
  • This pull request does not decrease project test coverage
  • If the code changes existing database collection(s), migration has been written
  • If UI texts are added or changed, all texts are internationalized

Reviewer checklist

Reviewed by: @matleppa @anarva

This list is to be completed by the pull request reviewer:

  • Code works as described/expected
  • Code seems to be error free
    • no browser console errors visible
    • no server console errors visible
    • passes CI build
  • Code is written in a way that promotes maintainability
    • easy to understand
    • well organized
    • follows project coding standards and conventions
    • well documented

- Add input
- Display count of found result
- Display No APIs found if it is
Copy link
Member

@matleppa matleppa left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Basically the functionality is there, however, some findings related to usability issues.

</h1>
</div>
<div class="col-xs-12 col-sm-4">
<input type="text" class="form-control pull-right" placeholder="Search" id="search-box">
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

About the search condition input:

  1. Placeholder: instead of plain text, make it localizable
    e.g.
    placeholder="{{_ 'searchField_placeholder' }}">

  2. Because the search is not incremental, but it needs a Enter key to be pressed, there needs to be a visible [Search] button on the right hand side of input field. That way the user gets a clue, what needs to be done.

  3. I think that the magnification glass symbol should also be included within th input field.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

1 and 3 points are done

});

Template.dashboardPage.events({
'change #search-box': (event, templateInstance) => {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could we get more convenient user experience with incremental search, if we used here keyup instead of change?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change event type to keyup. In this case it doesn't need to be a visible [Search] button on the right hand side of input field

@marla-singer
Copy link
Contributor Author

@matleppa The changes done

@matleppa matleppa merged commit 9d385c8 into develop Jan 31, 2018
@matleppa matleppa deleted the feature/search-box branch January 31, 2018 14:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants