-
-
Notifications
You must be signed in to change notification settings - Fork 212
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
"Resolve macro as..." code action produces unreadable text in pop up #1539
Comments
@ericdallo is this something we can solve in Calva without any change in clojure-lsp, you think? |
Yes, calva can handle |
It's a bit unclear to me how showDocumentRequest is related to this. It looks like in the default languageclient this is about showing documents rather than showing messages: |
Maybe you mean showMessageRequest? https://github.com/microsoft/vscode-languageserver-node/blob/f72faa0975cb2aaa85ce84da819944f84e1aac52/client/src/common/client.ts#L3401 I think this is what clojure-lsp uses: It seems reasonable that Calva shows a message on such a request, like the default client does, right? |
Yes, sorry, I meant |
IMO, the default one that vscode uses has a bad UX for multiple options |
Agreed. I am more thinking that from the semantics of showMessage it seems like the right choice. Seems like the server should be able to show a menu. Not that I find such an option from a quick scan. |
How can server show a menu? this should be done on client side right? |
Something like |
I see your point, the method name sounds odd, yeah, agreed |
I checked with people in the know and there is simply no such command. |
So... that was a bit more work than I had anticipated. But now we have this VSIX you can test: Looks like so: Followed by: |
When using the code action "Resolve macro as...", the text on the buttons in the pop up in the bottom right hand side of the screen is cut off, making them basically unreadable. Luckily this can be worked around via mouseover tool tips (although they're a bit finicky), but making this pop up more readable would be a nice usability improvement.
Screenshot taken when calling the code action on
clojure.test.check.properties/for-all
.Link to slack thread:
https://clojurians.slack.com/archives/CBE668G4R/p1645027436974109
Screenshot:
![image](https://user-images.githubusercontent.com/37941012/154307389-79626dc5-f060-4eca-82d4-cc7842185a0c.png)
The text was updated successfully, but these errors were encountered: