Revive VS Code DSC extension for YAML authoring
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 523
- Forks
- 75
- Avg merge
- 3d 16h
- Merged PRs (30d)
- 24
Description
Summary of the new feature / enhancement
As an end user,
I want IntelliSense and auto-completion when authoring DSC configuration files,
So that I can discover available resources and their properties without leaving my editor or consulting documentation.
Back in May 2025, the following PR was closed with the remark:
"We're prioritizing our Bicep extension work so I don't think we'll spend the effort to complete this one"
Now, with the drop in support on the Bicep extension, having something to author still matters for end users.
Proposed technical implementation details (optional)
Revive the VS Code DSC extension for YAML authoring
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the closed PR #448 and its discussion to recover the previous VS Code DSC extension approach. Identify the extension entry points and YAML authoring pieces described there, then define how resource and property IntelliSense should be exposed. Done means a working VS Code extension that provides DSC YAML completion and can be verified while authoring configuration files.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode, yaml
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 28/100