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

Query editor cursor end of line #1418

Closed
JohnWE opened this issue May 25, 2021 · 1 comment
Closed

Query editor cursor end of line #1418

JohnWE opened this issue May 25, 2021 · 1 comment

Comments

@JohnWE
Copy link

JohnWE commented May 25, 2021

Description

It is hard for me to navigate the query editor window with the arrow keys.

Reproduce Steps

Take this example:

Screenshot 2021-05-25 112024

I want to edit the company field. My cursor is at the end of line marked 3.

Press Up Arrow
Cursor is now at the middle of line marked 2. (:led_to)
Press Down Arrow
Cursor is now at the end of line marked 3.

We're skipping over the company line? I can't get to it.

Press Home
Cursor is at the start of line marked 3.
Press Up Arrow
Cursor is at the start of line marked 2.

Still can't get to the company line.

Expected Behavior

I would expect, since there are four lines of text here, pressing up would go move to the previous line, and not skip the company line.

Your Environment

software name version
OS Windows
Web browser
node.js
npm
yarn
Neo4j Browser 1.4.5
Neo4j 4.1.1
@OskarDamkjaer
Copy link
Contributor

OskarDamkjaer commented Jun 3, 2021

Thanks for taking the time to properly report this issue. While I agree it'd feel more natural to navigate the extra "fake" line created by the text editor wrapping like you suggested, I've not found a good way to accomplish it in the editor. To avoid the issue you can add more newlines to your query, to avoid the overflow. If I find a good way to solve it in the future, I'll post an update here.

If you think this is an issue you think we should prioritize, you open a feature request on canny and then we'll get a better feeling for how it compares to other feature requests.

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

No branches or pull requests

2 participants