Format generated code

[sahidvelji]

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.

[kriscoleman]

That's an interesting point.

I think for langauges with common tooling, like go fmt, it makes senes to do this.

however, for things like typescript, etc... formatters can be highly opinionated.

I typically use tools to generate code in my projects, and they rarely match my opinionated formatting. It is up to me as the user to ensure the generated file matches my formatting style post-generation.

🤔 I'll think on this some more. I'm leaning towards: implement standard formatting where applicable and update docs/cli-messages to encourage users of langauges without standard formatting to reformat post-gen.

[beeme1mr]

Perhaps we could add a flag at the generate level that allows you to run an arbitrary command after the generator is successful. For languages like go. We could pre-populate that post generate command to run the go formatter.

The nice part about that is it would be very flexible and you could define the post install command in the openfeature configuration file.