-
Notifications
You must be signed in to change notification settings - Fork 12.8k
Baseline completions and signature help #43049
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
Conversation
One suggestion is that the baseline is appended so that you can add multiple commands baseline to same file .. I think it would be useful if you want to edit a file and see completions or quick info after the edit |
Or it might be good to add a baselineAll variant that takes a list of baselines to produce. Another problem I thought of is that the completions baselines are large, so asking for completions at every marker is unneeded. |
{ | ||
"marker": { | ||
"fileName": "/tests/cases/fourslash/completionsCommentsClass.ts", | ||
"position": 599 |
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.
It would be good to have marker name or line and coloumn info as well.
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.
Name is quite easy to add, so I did that. I don't know of an easy way to convert positions back to line/columns, though.
Also rename another duped test filename.
Background: I need to update a lot of jsdoc tests since #41877 makes the jsdoc parse tree much more complete. This leads to a lot of painstaking, repetitive work updating fourslash tests.
In this PR, I add baselining to completions and signature help, to match the baselining for quick info. I also changed the filename, which should really be the containing filename.
Limitations