|
4 | 4 |
|
5 | 5 | The `main` branch of this repository contains the VS Code extension for Prisma schema files. Prisma package dependencies are kept up to date with [a GitHub Action workflow](/.github/workflows/1_check_for_updates.yml), that updates them every time a new version of them is released.
|
6 | 6 |
|
7 |
| -There is a stable version `prisma` and an unstable version `prisma-insider`. The stable one is published as ["Prisma" in the VSCode Marketplace](https://marketplace.visualstudio.com/items?itemName=Prisma.prisma), the unstable one as ["Prisma - Insider"](https://marketplace.visualstudio.com/items?itemName=Prisma.prisma-insider). An automated publish runs every 5 minutes calling the `check-update.sh` script. |
| 7 | +There is a stable version `prisma` and an unstable version `prisma-insider`. The stable one is published as ["Prisma" in the VS Code Marketplace](https://marketplace.visualstudio.com/items?itemName=Prisma.prisma), the unstable one as ["Prisma - Insider"](https://marketplace.visualstudio.com/items?itemName=Prisma.prisma-insider). An automated publish runs every 5 minutes calling the `check-update.sh` script. |
8 | 8 | In the beginning of this run, the CI job checks for Prisma stable version and `scripts/prisma_version_stable` contents to be the same. If the Prisma stable version is a new minor release, it makes the required version changes and proceeds further in the job. `scripts/prisma_version_stable` is a file that is committed by the stable CI job. That enables the future runs to know if an extension version is already published for a specific Prisma CLI version.
|
9 | 9 |
|
10 | 10 | If there is a new Prisma Patch, a new patch branch from the last stable release tag is created if it does not exist yet. It then makes the required version changes and releases a new Insider extension. This script also triggers the release of a new Stable extension, incrementing the version number each time.
|
@@ -38,21 +38,21 @@ On push to the `main` branch, a new Insider extension is released, with an incre
|
38 | 38 | - Run `npm run watch`.
|
39 | 39 | - Open VS Code on this folder.
|
40 | 40 | - Switch to the debug viewlet.
|
41 |
| -- Select `Launch VSCode extension` from the drop down. |
| 41 | +- Select `Launch VS Code extension` from the drop down. |
42 | 42 | - Run the launch config. (This will always use the local Language Server, not the published one.)
|
43 | 43 | - If you want to debug the server as well use the launch configuration `Attach to Server` afterwards.
|
44 |
| -- A new file should open in the [Extension Development Host] instance of VSCode. |
| 44 | +- A new file should open in the [Extension Development Host] instance of VS Code. |
45 | 45 | - Change the language to Prisma.
|
46 | 46 | - Make a change to the syntax
|
47 |
| -- To reload, press the reload button in VSCode (**Developer: Inspect TM Scopes** is helpful for debugging syntax issues) |
| 47 | +- To reload, press the reload button in VS Code (**Developer: Inspect TM Scopes** is helpful for debugging syntax issues) |
48 | 48 |
|
49 | 49 | ### Dependencies
|
50 | 50 |
|
51 | 51 | - the version of `@types/vscode` must always be smaller or equal to the `engines.vscode` version. Otherwise the extension can not be packaged.
|
52 | 52 |
|
53 | 53 | ## Debugging
|
54 | 54 |
|
55 |
| -- Set `prisma.trace.server` to `messages` or `verbose` to trace the communication between VSCode and the language server. |
| 55 | +- Set `prisma.trace.server` to `messages` or `verbose` to trace the communication between VS Code and the language server. |
56 | 56 | - There is a tool to visualize and filter the communication between Language Client / Server. All logs from the channel can be saved into a file, and loaded with the Language Server Protocol Inspector at https://microsoft.github.io/language-server-protocol/inspector
|
57 | 57 |
|
58 | 58 | ## Testing
|
|
0 commit comments