go-enum-encoding

What's Changed

• Generate Example Test by @nikolaydubina in https://github.com/nikolaydubina/go-enum-encoding/pull/31

Full Changelog: https://github.com/nikolaydubina/go-enum-encoding/compare/v1.7.0...v1.8.0

What's Changed

• Custom Methods by @nikolaydubina in https://github.com/nikolaydubina/go-enum-encoding/pull/30

Full Changelog: https://github.com/nikolaydubina/go-enum-encoding/compare/v1.6.2...v1.7.0

What's Changed

• gencode-line-semicolon by @nikolaydubina in https://github.com/nikolaydubina/go-enum-encoding/pull/29

Full Changelog: https://github.com/nikolaydubina/go-enum-encoding/compare/v1.6.1...v1.6.2

What's Changed

• Tailscale feedback by @nikolaydubina in https://github.com/nikolaydubina/go-enum-encoding/pull/28
• fixes issue with missing dot in generated code header line
• fixes issue with package level godoc is mixed with generated directive
• avoid malloc in String() method
• short version of String method
• conversion to string is efficient as conversion to []byte

Full Changelog: https://github.com/nikolaydubina/go-enum-encoding/compare/v1.6.0...v1.6.1

What's Changed

• added String() method by @nikolaydubina in https://github.com/nikolaydubina/go-enum-encoding/pull/27

Full Changelog: https://github.com/nikolaydubina/go-enum-encoding/compare/v1.5.0...v1.6.0

[!WARNING]
go:generate command is required to be immediately before var/const block with enum values

What's Changed

• Iota example by @nikolaydubina in https://github.com/nikolaydubina/go-enum-encoding/pull/23
• Support multiple enums in same file by @orenl in https://github.com/nikolaydubina/go-enum-encoding/pull/26

New Contributors

• @orenl made their first contribution in https://github.com/nikolaydubina/go-enum-encoding/pull/26

Full Changelog: https://github.com/nikolaydubina/go-enum-encoding/compare/v1.4.1...v1.5.0

• iota illustration

• illustration for iota

• short mode for inlining switch
• long mode example with currencies
• removed String
• encoding defines an array of byte slices

• generating benchmarks
• research for array loop benchmarks

• smaller code, [][2]string instead of map. removing convertion.

• no more json:"-" tag
• instead using json:"" tag

this is to simplify definition of empty values

1. Unknown is not a special word
2. Unknown is not required
3. empty value is optional and can be bound to any symbol name
4. if json does not match any values (including empty string, if any), then error

this effectively allows to have both options: A) error on empty values; or B) treat empty value as one of values.

bug fixes:

• when json tags strings have different ordering from symbol values ordering, ordering was breaking. now ordering is preserved.

• no log (which uses fmt)

• no fmt
• no bytes

• 120 LOC

• nit

• 100% coverage, no skipped errors

• even higher coverage

• even more test