codesandbox / codesandbox/codesandbox-client
Allow 'custom' (subdirectory) .devcontainer.json to be started
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 13.6k
- Forks
- 2.4k
- Avg merge
- 6d 19h
- Merged PRs (30d)
- 2
Description
🌈 Feature
At the moment only the default .devcontainer/devcontainer.json is used, but this in my case points to .devcontainer/default/devcontainer.json. I have multiple setup definitions, as is possible with Codespaces. Since the default is used, this causes a problem on startup, as at the moment #8752 prevents a start. An alternative would be to allow a more 'barebones' defintion, or allow a default (configurable) path to consider, like .devcontainer/codesandbox/ if exists.
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 tracing startup handling for the default .devcontainer/devcontainer.json, then review how the existing .devcontainer/default/devcontainer.json setup relates to issue #8752. Done means a custom subdirectory definition, such as .devcontainer/codesandbox/, can be selected or configured and startup no longer fails because only the default path is used.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100