gomodifytags VS kong

gomodifytags

https://github.com/fatih/gomodifytags - generate or modify struct tags

I suspect it's because Go's general philosophy is that it's better to be verbose and explicit (than terse and magical). Probably falls under "clear is better than clever" from Rob Pike's Go Proverbs: http://go-proverbs.github.io/

I think if this feature was added, it would not be with struct tags, but with an Encoder.SetFieldTransform(json.SnakeCase) or similar setting.

That might be quite a nice feature, actually. You could provide your own function to transform names when marshaling, and for unmarshaling it would strip punctuation and match case insensitively (because it's hard to do the reverse transform, for example should user_id go to UserId or UserID, and if the latter, how does the transform know?).

In any case, it seems like an issue was opened proposing something like that a couple of years ago (https://github.com/golang/go/issues/23027), and Russ Cox responded that the JSON package is basically done, but you could either fork it and add the feature, or use a tool that modifies struct tags like https://github.com/fatih/gomodifytags

I’ve been using https://github.com/alecthomas/kong for exposing generated protobuf structs for CLI args. How does your library compare?

I prefer https://github.com/alecthomas/kong these days

kong

We switched all our cli tools from cobra/viper to kong. I can highly recommend it. Almost no deps and easy to use, a great replacement for cobra in my opinion.

I switched all from viper to kong.

For all my commandline parsing and config loading needs I use kong. In contrast to Viper and Cobra it has almost no dependencies (while viper and cobra pull in half a jungle).

I think it is probably just a matter of personal taste, but I like to handle params and flags on the main function. I am probably biased by C experience and using https://github.com/alecthomas/kong though. Kong is certainly not as popular as cobra, but its approach.