Support devcontainer.json with build field #11943
Merged
+161
−1
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.
Plan: Support devcontainer.json with "build" field
Summary
Successfully added support for devcontainer.json files that use the "build" field instead of the "image" field.
Changes Made:
Added
DevcontainerBuildstruct to represent build configuration:dockerfile: Path to Dockerfilecontext: Build context pathargs: Build argumentsUpdated
DevcontainerConfigstruct:Build *DevcontainerBuildfield withomitemptytagImagefield to useomitemptytag to avoid empty string in JSONAdded comprehensive test (
TestEnsureDevcontainerConfigWithBuildField):Restored .devcontainer/devcontainer.json:
How It Works:
config = *existingConfig)omitemptyJSON tags ensure clean serialization (no empty fields in output)Test Results:
All devcontainer tests pass:
Original prompt
💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.