Internal: For PR / branches it would be great to have an easy way to test the VS Code extension
See original GitHub issueWe could
- build the extension and upload the
.vsixfile in the PR - do a release for each commit on PR / branches (maybe too complicated and option 1 is actually enough)
Issue Analytics
- State:
- Created 2 years ago
- Comments:9 (9 by maintainers)
Top Results From Across the Web
Testing Extensions - Visual Studio Code
Visual Studio Code supports running and debugging tests for your extension. These tests will run inside a special instance of VS Code named...
Read more >Code Reviews Using the Visual Studio Pull Requests Extension
This extension aims to make it easy for you to launch and view pull requests inside the integrated development environment (IDE) without needing ......
Read more >How to Create a Pull Request on GitHub using VS Code
In this blog, you will be given a walkthrough on how to make a PR (Pull Request) on GitHub using the editor Visual...
Read more >Pull Requests in VS Code - YouTube
Learn about the Pull Requests & Issues Extension in Visual Studio Code! | https://aka.ms/ vscode -gitTime Stamps:0:01 intro to pull requests ...
Read more >Remote Repositories for Visual Studio Code - YouTube
The Remote Repositories extension lets you quickly browse, search, edit, and commit to any remote GitHub repository directly from within ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

Did something with https://github.com/prisma/language-tools/pull/1110 seems to be working well so far, we can open new issues if we want to improve
undocumented but should work for us here https://github.com/prisma/language-tools/blob/main/packages/vscode/src/plugins/prisma-language-server/index.ts#L47:L47 So setting
process.env.PRISMA_USE_LOCAL_LS=trueshould actually make it possible to build the extension with the local language server