Skip to content
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

VSCode command mirroring #190

Open
TerminalFi opened this issue Jul 22, 2024 · 0 comments
Open

VSCode command mirroring #190

TerminalFi opened this issue Jul 22, 2024 · 0 comments

Comments

@TerminalFi
Copy link
Owner

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant