You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
I should note that I worked around it for now by using a separate generation directive for each type instead of one with multiple types. I've got 10+ types though, so this makes 10 separate files. I'd love to automatically put them into "generated_json_funcs.go" to match my "generated_strings.go" file.
wwsean08
added a commit
to wwsean08/jsonenums
that referenced
this issue
Jun 4, 2017
I just ran into this one as well. I would argue that the (desirable) -o option is not a fix but a workaround. For now I just have multiple go:generate lines. Sorry for no PR :(
Still a nifty tool Francesc -- thanks! :)
After running "
go generate
"a_jsonenums.go
contains the correct definitions for type A, butb_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.
The text was updated successfully, but these errors were encountered: