Gopher Robot submitted the change![Open in Gerrit]()
Change information
Commit message:
extension/src/language: document async behavior of input collect
Because vscode allow user to execute code actions while waiting
for user input, I thought it is necessary to have a mutex so only
one interactive refactoring can be executed and others should wait.
It would be very confusing if the extension ask one question from
the first interactive refactoring and then ask one question from
the other interactive refactoring. At least, we should finish all
questions from the first interactive refactoring then move to the
second.
However, it turns out that if the user request a new interactive
refactoring, a new vscode input box would automatically cancel the
existing active input box(if any). Our extension consider a
cancelled input box as a cancellation of the entire interactive
refactoring. So the previous interactive refactoring will be canceled.
This behavior is reasonable and maybe the best.
Since there is no code change required, this CL only modifies the
comments for documentation purpose.
For golang/go#76331
Change-Id: I1cba1c4ce17ecaa3ca516770939dbe8c4e13f8ac
Files:
- M extension/src/language/form.ts
Change size: S
Delta: 1 file changed, 16 insertions(+), 4 deletions(-)
Branch: refs/heads/master
Submit Requirements:
Code-Review: +2 by Peter Weinberger
TryBots-Pass: LUCI-TryBot-Result+1 by Go LUCI
Open in Gerrit
Gerrit-MessageType: merged
Gerrit-Project: vscode-go
Gerrit-Branch: master
Gerrit-Change-Id: I1cba1c4ce17ecaa3ca516770939dbe8c4e13f8ac
Gerrit-Change-Number: 742720
Gerrit-PatchSet: 4