-
Notifications
You must be signed in to change notification settings - Fork 63
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
Enable locstring navigation from LGV import form #1642
Conversation
…nto 1543_locstr_from_import
…nto 1543_locstr_from_import
…nto 1543_locstr_from_import
Can you enable it so that hitting the "enter key" performs the submit? |
Also, not really any fault of this PR or anything, just the history of this component, but it is unclear that using locstring is even something we'd be allowed to do because it suggests that we are only selecting "sequence" when really we want it to be a more generic thing that can handle refseq names, locstrings, and even gene features once name indexes are available |
What do you suggest could make this clearer? Changing the helper text or the labels? |
Yeah. Could also remove the open button. Then the LGV would open up either by choosing an option from the dropdown or hitting the enter key. |
Regarding making it clearer, in the import form is says "Select sequence to view" and there is a thing that says "sequence" wrapping the textbox In the LGV header bar it has no such helper text though I believe it should either have no helper text, or the helper text it has should say they can enter a sequence or locstring |
Codecov Report
@@ Coverage Diff @@
## master #1642 +/- ##
=======================================
Coverage 58.60% 58.61%
=======================================
Files 444 444
Lines 20385 20396 +11
Branches 4787 4786 -1
=======================================
+ Hits 11947 11955 +8
- Misses 8141 8147 +6
+ Partials 297 294 -3
Continue to review full report at Codecov.
|
not sure removing the open button would actually be the best user experience, seems like it would be easy for a user to fat-finger and enter the wrong thing, and then end up someplace else and get confused? what do you guys think? |
Ya I don't think I meant to remove the open button, I'd keep the open button but to allow as an option to hit the enter button to do the same action as open basically. |
fireEvent.keyDown(autocomplete, { key: 'ArrowDown' }) | ||
fireEvent.keyDown(autocomplete, { key: 'ArrowDown' }) | ||
fireEvent.keyDown(autocomplete, { key: 'Enter', code: 'Enter' }) | ||
expect(model.displayedRegions.length).toEqual(1) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice work on the testing. why are arrowdown needed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am testing the alternate search option from the dropdown.
https://github.com/GMOD/jbrowse-components/pull/1642/files#diff-82a164c4727a03a6f61491bcd006b102c68cd5f7ef74c19adfa73671fba37b61R87-R90 .Removed the arrow down and added test for open button.
Yeah, I can work on keeping both the submit on enter and on open click. Will add the button back in. 👍 |
Issue 1543
Follow up from issue 1509
Now able to open an LGV at a specific location from the import form
demo.mov