Small introduction to tags in Go
machiel.me
Small introduction to tags in Go
1–10 of 17 posts
Re: Small introduction to tags in Go
#2This should be handy for frameworks to do their own logic, but I would get very annoyed if I had to read code that was cluttered with tags.
Re: Small introduction to tags in Go
#3This is what I like about Go. This "small introduction" is basically everything there is to know about struct tags.
Bonus, Gorethink tags [0] and how we use them at Lavaboom [1].
0: https://github.com/dancannon/gorethink#encodingdecoding-stru...
Re: Small introduction to tags in Go
#4This should be handy for frameworks to do their own logic, but I would get very annoyed if I had to read code that was cluttered with tags.
Simplicity and minimalism are core values in Go, both in the language itself and the community and developers that use it, so clutter tends not to be a concern.
That aside, tags are currently in use in several ORM frameworks with a fair amount of success.
Re: Small introduction to tags in Go
#5At GopherCon, Kyle Erf and Sam Helman gave a great talk about struct tags, how some people are currently using them.
SourceGraph did a write up that summarized it very nicely. https://sourcegraph.com/blog/live/gophercon2015/123669868275
Re: Small introduction to tags in Go
#6tags are just strings. there is no spec tag whatsoever or syntax that can be validated at compile time.
A better solution would have been a proper annotation system that is part of the spec.
Re: Small introduction to tags in Go
#7At GopherCon, Kyle Erf and Sam Helman gave a great talk about struct tags, how some people are currently using them. SourceGraph did a write up that summarized it very nicely. https://sourcegraph.com/blog/live/gophercon2015/123669868275
the official GopherCon videos aren't posted yet, but you can find a recording of this talk here: https://www.youtube.com/watch?v=JVc-dTyXDAs
Re: Small introduction to tags in Go
#8tags are just strings. there is no spec tag whatsoever or syntax that can be validated at compile time. A better solution would have been a proper annotation system that is part of the spec.
This is the one problem.
Spent a whole day trying to figure out why only the first tag in the struct was 'active':
Name string `xml:"name", db:"name"` // Name string `xml:"name" db:"name"`
That along with my favorite: quote-wars. Many-a-time did I forget the quotes on the tag itself only to have it fail (without warning again...):
Name string `xml:name db:"name"` //Re: Small introduction to tags in Go
#9tags are just strings. there is no spec tag whatsoever or syntax that can be validated at compile time. A better solution would have been a proper annotation system that is part of the spec.
This is the one problem. Spent a whole day trying to figure out why only the first tag in the struct was 'active': Name string `xml:"name", db:"name"` // The answer was, going from memory, I added a comma (,) between the tags. Should have been: Name string `xml:"name" db:"name"` Stupid simple mistake, but really hard to track down. There was no compiler error, the second tag failed silently, and the first tag worked,…
The `go vet` tool will find these issues. Not ideal, but it will catch tag strings that compile but incorrectly formatted.
Re: Small introduction to tags in Go
#10tags are just strings. there is no spec tag whatsoever or syntax that can be validated at compile time. A better solution would have been a proper annotation system that is part of the spec.
This is the one problem. Spent a whole day trying to figure out why only the first tag in the struct was 'active': Name string `xml:"name", db:"name"` // The answer was, going from memory, I added a comma (,) between the tags. Should have been: Name string `xml:"name" db:"name"` Stupid simple mistake, but really hard to track down. There was no compiler error, the second tag failed silently, and the first tag worked,…
[deleted]