influxdata / influxdata/influx-cli
Revisit `overrides` for template/stack APIs
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 75
- Forks
- 22
- PR merge metrics
- No merged PRs in 30d
Description
In the rush to complete #4 and #18, I chose to override the entirety of the `template` and `stack` APIs so I could fix bugs & rearrange the schemas for codegen. Many of the fixes & improvements made there would make sense to backport to the `openapi` repo, to help out others & reduce the amount of duplication we're maintaining.
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
Compare the overridden `template` and `stack` APIs with the `openapi` repo, beginning with the fixes and schema changes made for code generation. Done means the useful fixes are backported to the `openapi` repo and duplication between the implementations is reduced.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, cli
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100