You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* Stale variables fix
* Introduced by #848
* Fixes#935
* Debugger QOL improvements and fixes
* Property rename to match expected behavior:
** members now do not have a prefix in object instances: Member/Foo -> Foo
** Inherited properties now do have a prefix: Parent1/Foo, ParentOfParent1/Boo
** Categories are properly treated and not displayed as property
* __repr__ support
** If the class contains __repr__ member, value of it will be used as a display name for it's instances representations. That works for Dictionary keys too.
Smaller changes and fixes:
* Arrays to display actual values for more complex types in preview (Vectors/Rects/etc)
* Strings are 'quoted' (similar to other DAPs)
* Rect2i fix (parse as int, not float)
* StrnigName better representation in values and dict keys: &'StringName'
* tasks discoverabilty: Added tasks for test and package to tasks.json.
* code cleanup & array support
* fix
* missed vscode_id for ObjectId
* some linter fixes
* CI: Godot version bump to 4.5.1
Test project: update test proj
* handling unset Godot Objects
* make sure to stop prev client
* test project to 4.6 update
Copy file name to clipboardExpand all lines: CONTRIBUTING.md
+3-2Lines changed: 3 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -12,6 +12,7 @@
12
12
2. Download dependencies by using the command `npm install`
13
13
3. When done, package a VSIX file by using the command `npm run package`.
14
14
4. Install it by opening Visual Studio Code, opening the Extensions tab, clicking on the More actions (**...**) button in the top right, and choose **Install from VSIX...** and find the compiled VSIX file.
15
+
5. Testing: `npm run test` to execute tests.
15
16
16
17
When developing for the extension, you can open this project in Visual Studio Code and debug the extension by using the **Run Extension** launch configuration instead of going through steps 3 and 4. It will launch a new instance of Visual Studio Code that has the extension running. You can then open a Godot project folder and debug the extension or GDScript debugger.
17
18
@@ -32,8 +33,8 @@ An example `workspace.code-workspace` file:
0 commit comments