You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
VS Code exposes a number of commands to the users which allow them to do specific tasks easily. One of these commands is /tests which seems like a unique capability. This appears like it might require some unique handling.
In VS Code these come back as workspaceEdits another LSP response
{
"type": "workspaceEdit",
"workspaceEdit": [
[
{
"$mid": 1,
"external": "untitled:test_Untitled-1",
"path": "test_Untitled-1",
"scheme": "untitled"
},
[
{
"range": [
{
"line": 0,
"character": 0
},
{
"line": 0,
"character": 0
}
],
"newText": "## Tests\n\nHere are some test cases for your code:\n\n1. Test case 1:\n - Input: [input here]\n - Expected output: [expected output here]\n\n2. Test case 2:\n - Input: [input here]\n - Expected output: [expected output here]\n\n3. Test case 3:\n - Input: [input here]\n - Expected output: [expected output here]\n\nYou can add more test cases as needed to thoroughly test your code."
}
]
]
]
}
We need to determine how these requests are made, and if the copilot.vim supports these
The text was updated successfully, but these errors were encountered:
VS Code exposes a number of commands to the users which allow them to do specific tasks easily. One of these commands is
/tests
which seems like a unique capability. This appears like it might require some unique handling.In VS Code these come back as
workspaceEdits
another LSP responseWe need to determine how these requests are made, and if the copilot.vim supports these
The text was updated successfully, but these errors were encountered: