When sending the chat command multiple times to devchat, it results in jumbled chat output. It's required to wait for one chat session to end before initiating another. This issue often occurs when triggering the command via the right-click context menu or through codelens buttons, indicating a need for a pre-execution check to determine if it's possible to send another chat command.
Steps to Reproduce
Initiate a chat session using the chat command through the right-click menu or codelens button.
Without waiting for the current session to end, initiate another chat session using the same method.
Observe that the chat output becomes confused and unreadable.
Expected Behavior
There should be a way to either queue the chat commands or prevent a new command from being sent until the current session has completed, ensuring that chat output remains coherent and understandable.
Possible Solution
Implementing a check before each chat command execution to verify if another chat session is still active. If so, either queue the command or notify the user that they must wait for the current session to end before initiating a new one.
When sending the chat command multiple times to devchat, it results in jumbled chat output. It's required to wait for one chat session to end before initiating another. This issue often occurs when triggering the command via the right-click context menu or through codelens buttons, indicating a need for a pre-execution check to determine if it's possible to send another chat command.
Steps to Reproduce
Expected Behavior There should be a way to either queue the chat commands or prevent a new command from being sent until the current session has completed, ensuring that chat output remains coherent and understandable.
Possible Solution Implementing a check before each chat command execution to verify if another chat session is still active. If so, either queue the command or notify the user that they must wait for the current session to end before initiating a new one.