-
Notifications
You must be signed in to change notification settings - Fork 18k
x/tools/gopls: multiline strings should be foldable in the editor #49554
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
Comments
This is a good suggestion, and I think it's a good candidate for external contribution. Marking as help-wanted, though @ansaba might be interested in taking this. |
I'd like to try to take this one on. It'd be my first contribution (already followed the contribution guide). What's my next step? |
The relevant code place is https://go.googlesource.com/tools/+/refs/heads/master/internal/lsp/source/folding_range.go For tests, modifying the existing source_test.go and add test data for the new case here will be sufficient. And, please check the instruction for gopls contributors. |
This commit adds support for detecting multiline strings for folding ranges. Ref: golang/go#49554
Hey I worked on implementing this at golang/tools#354 |
This commit adds support for detecting multiline strings for folding ranges. Fixes golang/go#49554
This commit adds support for detecting multiline strings for folding ranges. Fixes golang/go#49554
Change https://golang.org/cl/372414 mentions this issue: |
This commit adds support for detecting multiline strings for folding ranges. Fixes golang/go#49554
Is your feature request related to a problem? Please describe.
Some multiline strings needlessly take up space in the editor and it is not possible to fold them into a single line.
Describe the solution you'd like
Every multiline string should become a foldable region.
Describe alternatives you've considered
I quickly checked available extensions, but there doesn't seem to be one for this exact use case.
Additional context

The text was updated successfully, but these errors were encountered: