I ran into an issue that was annoying to track down and I'm not sure I entirely get it. I was using jsonenums as part of a nested struct slice, and explicitly setting the json field name & setting the omitifempty flag. My observation was that if I built an instance of that struct explicitly setting the value to be iota 0 as documented in the shirtsize example project, the value during encoding would be removed entirely. If I removed the omitifempty flag, the proper value would show up. Likewise I could also work around it by just adding 1 to the iota const. It may be worth further investigation and/or a simple documentation update to warn people about this.

I was able to track it as far as here in the golang encode library. My gut is telling me somewhere there is a confusion between an iota value of 0 and a nil which is what I expect omitifempty to apply to.

I've found it useful to access the _TypeNameToValue map in the generated code from other places in my package (probably not best practice), but if I remove the generated file and rerun go generate again it will cause an undeclared name error.

Perhaps it would be useful to allow a list of files as arguments to jsonenums to limit what it parses as apart of the package, i.e. jsonenums -type myType ...files Then we could use a line such as:

//go:generate jsonenums -type=myType $GOFILE

in the file that contains the type declaration.

A typical use for me is

const (
    Foo T = iota
    Bar
    Baz
)

but this forces the JSON strings to be "Foo" etc, not "foo", which is not very friendly to the human. Could there be a -lowercase flag or such?

I'm not 100% sure what's the best way to handle CamelCaseWords in general. Should that, with -lowercase, become "camelCaseWords", "camelcasewords", "camel_case_words", or what?

Sorry, I really do not know how to use this? I put the //go:generate jsonenums -type=OnlineType in the file. Then I input go generate. It doesn't work. Is there anyone who can teach me?

Started getting this after updating to go1.7:

2016/08/18 14:31:01 parsing package: type-checking package: client.go:9:2: could not import io (reading export data: /usr/lib/go/pkg/linux_amd64/io.a: unknown version: v1io'$GOROOT/src/io/io.go*SeekStart*%Seek)

I tried to rebuild jsonenums and update golang.org/x/tools/... but no avail.

As per title.
Also add thanks, very useful.

type Fruit int
const (
     Apple Fruit = iota
     Banana
     Orange
)

I'd like the strings to be "apple", "banana", "orange". How can I assign custom strings ?

Something like this would work ?

type Fruit int
const (
     Apple Fruit = iota  `"apple"`
     Banana                  `"banana"`
     Orange                  `"orange"`
)

Hello there!

I don't know if there is still any support but I am having an error:

emixam23@Emixam23-PC:~/xxx$ make regenerate-enums 
jsonenums -type=AccountType xxx/enums.go
2021/09/15 17:19:48 parsing package: provided directory (/home/emixam23/xxx/internal/domain/enums/enums.go) may not under GOPATH (/home/emixam23/xxx): cannot find package "." in:
        /home/emixam23/xxx/internal/domain/enums/enums.go
make: *** [Makefile:59: regenerate-enums] Error 1

It seems like I can't provide a path to the given enums go file

best,

Max

If you use a colon-separated GOPATH, the logic at https://github.com/campoy/jsonenums/blob/master/parser/parser.go#L33 breaks pretty badly.

//go:generate jsonenums -type=A,B

package main

type A int
const (
   X A = iota
   Y
   Z
)

type B int 
const (
   M B = iota
   N
   O
)

After running "go generate" a_jsonenums.go contains the correct definitions for type A, but b_jsonenums.go has the definitions for both type A and type B.

What I would like best is a way to dump all of the generated json into just one fil like stringer's -o flag allows me to do.