Represent nested workspaces and subproject target slices
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 1
- Forks
- 0
- Avg merge
- 8m
- Merged PRs (30d)
- 1
Description
Problem
Large repos have nested packages and workspace-like layouts. A single root module map is not enough.
Needed
- Represent subprojects/nested build packages.
- Allow target selection inside a repo without building every sample/tool.
- Record package-local roots and relative output locations.
- Keep diagnostics scoped to the subproject that failed.
Corpus drivers
- MicroZig has many nested build packages.
- zig-gamedev has samples/experiments with optional dependencies.
- Mach has examples/editor/modules.
Done when
- Corpus manifests can name a target slice like
samples/minimal_*orport/<chip>without overbuilding the repo. --buildand future--parityreports include the selected target path.
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 with the corpus manifest handling and the --build reporting path, then trace how target selection and package roots are represented. Use the MicroZig, zig-gamedev, and Mach layouts as reference cases; done means manifests can select nested target slices without overbuilding and reports include the selected target path.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python, zig
- Domain
- build-system, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100