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

improve search #535

Closed
wants to merge 1 commit into from
Closed

improve search #535

wants to merge 1 commit into from

Conversation

avsingh999
Copy link
Member

@avsingh999 avsingh999 commented Apr 14, 2019

Fixes #520 (<=== Add issue number here)

Make sure these boxes are checked before your pull request (PR) is ready to be reviewed and merged. Thanks!

  • PR is descriptively titled 📑 and links the original issue above 🔗
  • tests pass -- look for a green checkbox ✔️ a few minutes after opening your PR -- or run tests locally with rake test
  • code is in uniquely-named feature branch and has no merge conflicts 📁
  • screenshots/GIFs are attached 📎 in case of UI updation
  • ask @publiclab/reviewers for help, in a comment below

We're happy to help you get this ready -- don't be afraid to ask for help, and don't be discouraged if your tests fail at first!

If tests do fail, click on the red X to learn why by reading the logs.

Please be sure you've reviewed our contribution guidelines at https://publiclab.org/contributing-to-public-lab-software

Thanks!

@codeclimate
Copy link

codeclimate bot commented Apr 14, 2019

Code Climate has analyzed commit b99d41f and detected 0 issues on this pull request.

View more on Code Climate.

@avsingh999
Copy link
Member Author

@jywarren @sashadev-sky @SidharthBansal @gauravano @publiclab/is-reviewers please review
thanks : )

@sashadev-sky
Copy link
Member

@avsingh999 this issue already has a PR open for it at #511 , so I am going to close it. Please contribute there by providing a review if you have additional thoughts on it! Thank you and sorry to close this one on you

@sashadev-sky
Copy link
Member

@avsingh999 I misspoke! I see you are not working on the same issue as @divyabaid16. Reviewing now

@@ -22,6 +22,26 @@
<%= render 'layouts/footer' %>

<script>
$("input#search-input").on({
keydown: function(e) {
if (e.which === 32)
Copy link
Member

Choose a reason for hiding this comment

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

the which attributes has been deprecated in favor of the key attribute. It's now compatible across all browsers (see here) so lets start using it? I think the replacement would be e.key === " " but please double check!

Copy link
Member Author

Choose a reason for hiding this comment

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

@avsingh999 I requested some changes! Let me know your thoughts.

Also can you please open a new issue for this and reference it instead of the current one you're referencing. It makes it a lot easier to review and people are less likely to duplicate issues in this case

@sashadev-sky Sorry I had added wrong issue number. #520 is correct.
thank you

@@ -22,6 +22,26 @@
<%= render 'layouts/footer' %>

<script>
$("input#search-input").on({
Copy link
Member

Choose a reason for hiding this comment

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

I think this is better moved into a separate file rather than application.html.erb, to stick with modularity

Copy link
Member Author

Choose a reason for hiding this comment

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

@sashadev-sky I also think But I don't find any file to add this,So I was thinking to add all script in new .js file.
thank you : )

@sashadev-sky
Copy link
Member

@avsingh999 I requested some changes! Let me know your thoughts.

Also can you please open a new issue for this and reference it instead of the current one you're referencing. It makes it a lot easier to review and people are less likely to duplicate issues in this case

@avsingh999
Copy link
Member Author

@avsingh999 I requested some changes! Let me know your thoughts.

Also can you please open a new issue for this and reference it instead of the current one you're referencing. It makes it a lot easier to review and people are less likely to duplicate issues in this case

@sashadev-sky Sorry for this i have added wrong issue number.#520 is correct

@sashadev-sky
Copy link
Member

@avsingh999 No problem! I like the plan to move it into a new js file. Mention me for another review when you're ready 👍

@sashadev-sky
Copy link
Member

@avsingh999 im going to close this because I think it's been abandoned and the implementation wasn't up to a point where it was working. Please feel free to reopen if you decide to come back to it! Note that some changes were made towards this since you opened this issue in #630

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

Successfully merging this pull request may close these issues.

Search by Space/blank should stop
2 participants