open-feature / open-feature/cli
Format generated code
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 63
- Forks
- 22
- Avg merge
- 1h 27m
- Merged PRs (30d)
- 19
Description
After running openfeature generate go, I expected the generated .go file to be formatted. I have not tried generating code for the other languages, but regardless, all generated code should be formatted. For Go, the choice of formatter is easy: Go has a builtin formatter go fmt. For other languages, it may make sense to evaluate each individually and use whatever formatter is most commonly used and recommended in the community. For example, we might use ruff for Python.
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 the openfeature generate go command and inspect how generated .go files are written. Verify the output with Go's go fmt; done means Go output is formatted and the project has a decided formatter approach for other generated languages, including Python.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100