Skip to content

Commit fdd4e35

Browse files
committed
test
1 parent 3011ca3 commit fdd4e35

File tree

5 files changed

+106
-20
lines changed

5 files changed

+106
-20
lines changed

README.md

Lines changed: 10 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -2,30 +2,20 @@
22

33
Experimental project for running Source Academy within Visual Studio Code.
44

5-
## How to use
5+
## Installing
6+
7+
If you don't have VS Code installed, head over to the official docs: https://code.visualstudio.com/docs/setup/setup-overview
68

7-
TODO: Add instructions
9+
Ensure that your VS Code version is 1.93.0 and above.
810

9-
## Notes to developers
11+
Head over to https://marketplace.visualstudio.com/items?itemName=source-academy.source-academy
1012

11-
### Running the extension in dev mode
13+
## How to use
1214

13-
1. Setup the project
14-
```
15-
yarn
16-
```
17-
1. Compile
18-
```
19-
yarn compile
20-
```
21-
1. Run the extension in debug mode by opening the root folder a VSCode window, then "Start Debugging" (or press F5).
15+
After installing the extension, the Source Academy sidebar should appear.
2216

23-
### Publishing the extension
17+
Launch the Source Academy panel.
2418

25-
For a new release, update the version in `package.json` and tag the commit. Push the commit and the tag to the repo,
26-
which will trigger GitHub Actions to build and publish the extension to Releases tab and the Marketplace.
19+
![[starting.png]]
2720

28-
```
29-
npm version (major|minor|patch)
30-
git push origin main --tags
31-
```
21+
After the panel loads, you can log in and begin coding by heading to any of the assesssments.

docs/README.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
## Notes to developers
2+
3+
### Running the extension in dev mode
4+
5+
1. Setup the project
6+
```
7+
yarn
8+
```
9+
1. Compile
10+
```
11+
yarn compile
12+
```
13+
1. Run the extension in debug mode by opening the root folder a VSCode window, then "Start Debugging" (or press F5).
14+
15+
### Publishing the extension
16+
17+
For a new release, update the version in `package.json` and tag the commit. Push the commit and the tag to the repo,
18+
which will trigger GitHub Actions to build and publish the extension to Releases tab and the Marketplace.
19+
20+
```
21+
npm version (major|minor|patch)
22+
git push origin main --tags
23+
```

docs/developer-guide.md

Lines changed: 70 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,70 @@
1+
# Developer Guide
2+
3+
We place developer-facing stuff here because the README.md in the root will be displayed on VS Code Marketplace.
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+
1. Setup the project
15+
```
16+
yarn
17+
```
18+
1. Compile
19+
```sh
20+
yarn compile
21+
```
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+
```
30+
31+
## Publishing the extension
32+
33+
For a new release, update the version in `package.json` and tag the commit. Push the commit and the tag to the repo,
34+
which will trigger GitHub Actions to build and publish the extension to Releases tab and the Marketplace.
35+
36+
```sh
37+
npm version (major|minor|patch)
38+
git push origin main --tags
39+
```
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

src/extension.ts

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -27,6 +27,9 @@ export function activate(context: vscode.ExtensionContext) {
2727
// };
2828
const info = context.globalState.get("info") ?? {};
2929

30+
context.globalState.update("assessmentOverviews", undefined)
31+
context.globalState.update("courseId", undefined)
32+
3033
client.sendRequest("source/publishInfo", info);
3134

3235
SOURCE_ACADEMY_ICON_URI = vscode.Uri.joinPath(

starting.png

99.5 KB
Loading

0 commit comments

Comments
 (0)