lloyd
New Contributor
Joined 5 years ago
User Profile
User Widgets
Contributions
[Go] why the JSON tags everywhere
Many (almost all) struct types defined in the code generated by the swagger-codegen Go target have tags specifying how their fields should be marshaled into JSON. These are not the models being generated, these are types that are never marshaled in any way as far as I can tell. This can't be API related because there are no equivalent XML tags. Is it just that the original author pasted them in from somewhere else without realising what they are for? I don't expect Java programmers to pay much attention to this sort of feature of Go, so it's feasible I guess. Here is an example that also shows some of the inconistency at play as well. type BasicAuth struct { UserName string `json:"userName,omitempty"` Password string `json:"password,omitempty"` } type APIKey struct { Key string Prefix string }Why "linger" a context.Context in the codegen Go client?
Hi all, Does anyone know why the go client generates the following code for each API? // Linger please var ( _ context.Context ) The documentation for the context package doesn't mention any behind the scenes machinery that would benefit from this code construct and in fact it strongly implies that programs should not try and store long lived Context objects. I've Googled for this code construct elsewhere and I don't see anything. Cheers