Documented Developer Setup and Folded in VS Code Section - #28
Merged
Conversation
Added a new "Developer Setup" article to the developer manual (`docs/developer-manual/tooling/developer-setup.md`), with a subsection per tool: installing the pinned .NET SDK and restoring local `dotnet` tools, installing Node.js and the pinned dprint, CSpell, and MarkdownLint-cli2 versions, and installing Visual Studio Code with its recommended extensions. The Visual Studio Code subsection explains why Workspace Config Plus is not just recommended but required in practice — without it, no `settings.json` is generated at all, so the shared editor configuration silently never applies. `README.md` gained a "Developer Setup" section, first under "Development", listing the tools required or recommended without installation instructions and pointing at the new article. Its old "Visual Studio Code" subsection, which explained the Workspace Config Plus mechanism at length, was folded into the new article and removed from the read me. Linked the new article from the tooling and developer-manual indexes, and added a `CLAUDE.md` routing table row for it. This work was done with the help of Claude Code, which wrote the new article and updated `README.md`, `CLAUDE.md`, and the indexes to match. Co-Authored-By: Claude <noreply@anthropic.com>
lecode-official
added
the
Type: Documentation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added a new "Developer Setup" article to the developer manual (
docs/developer-manual/tooling/developer-setup.md), with a subsection per tool: installing the pinned .NET SDK and restoring localdotnettools, installing Node.js and the pinned dprint, CSpell, and MarkdownLint-cli2 versions, and installing Visual Studio Code with its recommended extensions. The Visual Studio Code subsection explains why Workspace Config Plus is not just recommended but required in practice — without it, nosettings.jsonis generated at all, so the shared editor configuration silently never applies.README.mdgained a "Developer Setup" section, first under "Development", listing the tools required or recommended without installation instructions and pointing at the new article. Its old "Visual Studio Code" subsection, which explained the Workspace Config Plus mechanism at length, was folded into the new article and removed from the read me. Linked the new article from the tooling and developer-manual indexes, and added aCLAUDE.mdrouting table row for it.This work was done with the help of Claude Code, which wrote the new article and updated
README.md,CLAUDE.md, and the indexes to match.Closes issue #27.