5.2 VS Code / Code [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== 5.2 VS Code / Code ======

[[fxdemo:05-part:start | Go To Top ]]

[[fxdemo:05-part:05-development-environment:start | Return to Development Environment ]]

The Phase 0 development environment should support Visual Studio Code, commonly invoked from the command line as ''code'', as the recommended editor for team development. VS Code should not define the architecture, but it can help the team standardise editing, formatting, file navigation, terminal use, script execution, and [[dido:99_annexes:annex-b-terms-and-definitions:r:repository|Repository]] inspection.

The Repository may include a ''.vscode'' directory containing workspace recommendations. This directory may contain recommended extensions, workspace settings, launch [[dido:99_annexes:annex-b-terms-and-definitions:c:configuration|Configurations]], and task definitions that support Phase 0 development. Shared VS Code settings should improve consistency without embedding personal preferences that would interfere with other developers.

The team should use VS Code settings to support practical development, such as file associations, formatting conventions, shell task shortcuts, script execution tasks, and visibility of generated files. Developers should not rely on VS Code-specific behaviour that prevents the Repository from being built, run, or [[dido:99_annexes:annex-b-terms-and-definitions:v:validation|Validated]] from the command line.

The ''code'' command should remain optional unless the team explicitly promotes it to a required tool. A developer should be able to clone the Repository, check prerequisites, generate [[dido:99_annexes:annex-b-terms-and-definitions:t:type|Types]], build containers, run [[dido:99_annexes:annex-b-terms-and-definitions:n:node|Nodes]], stop Nodes, and inspect logs without depending on editor-specific actions.

----

<WRAP centeralign>

© 2026 Dido Solutions, Inc. and Jackrabbit Consulting, Inc.

</WRAP>