oxidecomputer / oxidecomputer/oxide.go
Create object types from schema instead of plucking them out of the paths
Open
Nobody has claimed this yet.
Enhancement
Go SDK
- Dominant language
- Go
- Stars
- 26
- Forks
- 6
- Avg merge
- 5h 33m
- Merged PRs (30d)
- 9
Description
The current implementation makes duplication pretty easy and the code unnecessary complicated
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
The issue does not name files, tests, or an entry point. Start by locating the code that derives object types from API paths and the schema source, then compare their responsibilities and duplication; done means object types are created from the schema rather than being plucked from paths.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100