This is a long-term feature request and will require a ton of research. Would be nice to allow any snippet to be written in any programming language.

When right-clicking and dragging in the graph, the developer can translate the graph space to view different areas. The mouse is hidden and locked to allow for limitless movement. However, on release, the mouse is placed in the center of the viewport. This should be restored to the position where the developer clicked in the viewport.

The snippet window editor will highlight which line the debugger is paused at. If this window is closed and reopened, the highlight disappears. Should be able to query the line and restore the highlight.

Developers should be able to connect to a hosted workspace and be able to collaboratively work on a project in real-time. Lots of investigation is needed.

Breakpoints are stored in a PDB file. The remote debugging session reads the breakpoints from this file. However, any lines that were deleted that had breakpoints set will not properly update the Snippet in memory and thus, the PDB file. The deleted breakpoints is properly reflected in the snippet editor.

The developer is able to interact with both an open Snippet window and the underlying graph or node. The Snippet window should block this input.

Need to setup a framework to begin unit testing the internals of Snippet. This is not associated with the developer facing unit test feature.

If a step is performed at the end of a snippet, the next snippet is run but does not break. This should break similar to stepping into a function in traditional languages.

Currently, all logs received from the debug server are emitted as Info logs. The type of log should be given with the contents for the client to properly display in the Output window.

There is currently a leak regarding SnippetData on exit when two nodes are connected to each other to form a circular dependency.

The following error and warning are reported:

ERROR: ~List: Condition "_first != __null" is true.
   At: ./core/self_list.h:112.

WARNING: cleanup: ObjectDB instances leaked at exit (run with --verbose for details).
   At: core/object.cpp:2132.

Lua comments are not properly highlighted in the text editor. This should be handled by the LuaSyntaxColors resource.

The auto-complete window only displays Lua keywords in the window. This should be extended to Lua defined libraries and functions, along with declared variables.

Need to update the godot-headers/godot-cpp native bindings to use the latest version of Godot. Would be nice to print out the commit hash that each module is being built against.

Each snippet comes with a Unit Test tab to add unit tests that can be run for the snippet. This area should be used to define any data the snippet relies on and should also allow the developer to define what are valid and invalid results. Some research is needed to determine how to start with version 1 of this feature.

The snippet window doesn't highlight any string literal text.

If a snippet contains a procedure call to a function that doesn't exist, an output pin should be generated so that a new snippet can be created to define the implementation of this function.