|
1 |
| -# Developer Guide |
| 1 | +# Notes to developers |
2 | 2 |
|
3 |
| -We place developer-facing stuff here because the README.md in the root will be displayed on VS Code Marketplace. |
| 3 | +## Running the extension in dev mode |
4 | 4 |
|
5 |
| -## Setting up project locally |
6 |
| -1. Clone this repo |
7 |
| -2. Assume yarn installed. Assume node installed. |
8 |
| - |
9 |
| -For Nix users, step 2 |
10 |
| -- If you have nix-direnv installed, no need anything |
11 |
| -- Else, enter with nix develop |
12 |
| - |
13 |
| -## Running the extension (in?) |
14 | 5 | 1. Setup the project
|
15 | 6 | ```
|
16 | 7 | yarn
|
17 | 8 | ```
|
18 | 9 | 1. Compile
|
19 |
| - ```sh |
| 10 | + ``` |
20 | 11 | yarn compile
|
21 | 12 | ```
|
22 |
| -1. Run the extension in debug mode by opening the root folder in VS Code, then "Start Debugging" (or press F5). Under the hood, this is will compile the extension by running `yarn compile`. |
23 |
| - |
24 |
| -Alternatively, install a compiled version of the extension. |
25 |
| - |
26 |
| -```sh |
27 |
| -yarn compile |
28 |
| -code --profile "Default" --install-extension source-academy-*.vsix --force |
29 |
| -``` |
| 13 | +1. Run the extension in debug mode by opening the root folder a VSCode window, then "Start Debugging" (or press F5). |
30 | 14 |
|
31 | 15 | ## Publishing the extension
|
32 | 16 |
|
33 | 17 | For a new release, update the version in `package.json` and tag the commit. Push the commit and the tag to the repo,
|
34 | 18 | which will trigger GitHub Actions to build and publish the extension to Releases tab and the Marketplace.
|
35 | 19 |
|
36 |
| -```sh |
| 20 | +``` |
37 | 21 | npm version (major|minor|patch)
|
38 | 22 | git push origin main --tags
|
39 | 23 | ```
|
40 |
| - |
41 |
| -What else? |
42 |
| -- Key points from my FYP report, including architecture |
43 |
| -- For extension: tip to console.log, using debugger |
44 |
| -- Instructions for local frontend (tip: how to log), and for LSP (tip: how to log) |
45 |
| -- ensure vscode version |
46 |
| -``` |
47 |
| -"engines": { |
48 |
| - "vscode": "^1.93.0" |
49 |
| - }, |
50 |
| -``` |
51 |
| - |
52 |
| -it is my beleif that we should have good dev experience |
53 |
| - |
54 |
| -note to developers: if following vscode debug setup doesn't work, this is a documentation bug. if you are sure you followed the steps correctl,y please raise an issue |
55 |
| - |
56 |
| -it is my beleif that we should have good dev experience |
57 |
| - |
58 |
| -iamge to readme, user facing |
59 |
| - |
60 |
| -About debuggin in vscode is supported for VS Code, but not neovim. |
61 |
| - |
62 |
| -add exrc for neovim |
63 |
| - |
64 |
| -sugested extensions: both to user and to developer |
65 |
| - |
66 |
| -## Archi |
67 |
| -Delegation to frontend |
68 |
| -js-slang in frontend |
69 |
| -Extension context and Webview context |
70 |
| -Drawing from STEPS |
0 commit comments