-
Notifications
You must be signed in to change notification settings - Fork 408
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
Do not show signature help at the end of an invocation #2079
Conversation
The change works well for me. I just noticed some exceptions thrown when we get into some really weird cases like : (cursor at
I was wondering why the logic in the first if statement isn't just used to cover the else. Either way, I would probably just try to avoid hitting the error. |
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.
Did you try without breakpoints? There's a cancellation check for the monitor if you look at SignatureHelpContext#resolve(..)
. In many cases dealing with popups in the UI, simply switching away from the UI being tested is enough to trigger the cancellation. If you set your breakpoint after the cancellation checks, maybe you'll run into the issue ?
Change looks good to me.
- for example, when it's "foo()|", we should not show the signature help. Signed-off-by: sheche <[email protected]>
6e6f747
to
e077ed8
Compare
for example, when it's
foo()
, we should not show the signature help.Signed-off-by: sheche [email protected]