-
Notifications
You must be signed in to change notification settings - Fork 30k
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
Test and iterate on TS expandable hover apis #232685
Comments
Tagging @gabritto about the following I followed the steps in order to use the TypeScript compiler from the branch. Some feedback I have: In the vscode repo on line 202 of the file
Screen.Recording.2024-10-31.at.15.47.58.movI think it would be good generally to change the API so that we allow linkification of markdown text for the purpose of expansion. Perhaps in the coming iterations, I can develop this, if there is sufficient need for this to be put into the iteration plan. cc @alexdima |
Thanks for the feedback. I removed truncation of the hover content on the TSServer side when expandable hovers are requested, so I think that's happening on the vscode side. |
I see thanks for letting me know, I'll have a look to remove truncation of hovers. I will discuss this issue with my manager to see if we should place the linkification of markdown text into the iteration plan and work on it. I suppose also we could do a test pass on this perhaps during release week to get feedback about this. |
Hi I discussed this with my manager. Could we merge and publish the TypeScript branch work to production so we can self-host easily on the work in VS Code? |
Hey @aiday-mar, the PR was merged yesterday afternoon. You all should be able to pick it up in the current nightly ( |
Hi @DanielRosenwasser thanks for letting me know, I will upgrade the TypeScript version |
Here is the list of feedback I received. I will update this list as more feedback is received:
|
To try it:
"typescript.experimental.expandableHover": true
Let's test out TS's current implementation of expandable hovers. The main question is if the UI is good enough as-is, or if it turns out we need something different, which may require API changes
The text was updated successfully, but these errors were encountered: