Question 1

How do I use go-enum with go generate?

Accepted Answer

Add a //go:generate comment to your Go file, such as //go:generate go tool go-enum --marshal, then run go generate. This automates enum generation as part of your build process, detailed in the Adding it to your project section.

Question 2

go-enum vs stringer: which is better for Go enums?

Accepted Answer

go-enum offers more features like JSON marshaling and SQL integration out-of-the-box, while stringer is simpler and part of the Go toolchain. Choose go-enum for comprehensive functionality or stringer for basic string conversion only.

Question 3

Can go-enum handle string enums stored as integers in SQL?

Accepted Answer

Yes, use the --sqlint flag to generate code that stores string enums as integers in databases, allowing string usage in APIs while using integers in SQL, as explained in the String typed enums section.

Question 4

How to add custom methods to go-enum generated code?

Accepted Answer

You can use custom templates with the -t flag to extend the generator. Create a template file with your additional methods, and go-enum will incorporate them into the output, mentioned in the Custom Templates feature.

Question 5

Does go-enum support YAML or other serialization formats?

Accepted Answer

No, go-enum only provides built-in support for JSON and SQL. For other formats like YAML or XML, you need custom implementations or external libraries, as it's not covered in the features.

Question 6

What are the performance impacts of using go-enum?

Accepted Answer

The generated code uses maps for string parsing, adding minimal runtime overhead. Compile-time increase is negligible, and benefits like reduced boilerplate often outweigh any costs.

go-enum

What is go-enum?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions