oxidecomputer / oxidecomputer/progenitor
prune types that are generated, but not referenced from any operation
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1k
- Forks
- 136
- Avg merge
- 8h 36m
- Merged PRs (30d)
- 14
Description
Typify can generate types that are unreachable from any progenitor interface. How? In some cases, typify can get pretty fancy and infer useful structure from referenced types. For example, there may be named, referenced types that are used as the variants of a oneOf. In that case, typify may generate both the referenced types and, effectively, partial copies of those types embedded within an enum.
Only types directly or transitively referenced by operations actually need to be in the final code.
Contributor guide
No contributing guide indexed for this repository
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 Typify's type-generation and operation-reference traversal, then inspect how named types and oneOf variants become generated types. Verify the reachability cases described in the issue, including transitive operation references and embedded partial copies; done means unreachable types are omitted while all operation-reachable types remain.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100