Problem with swagger and omitempty on json structs about go-restful HOT 3 CLOSED

Just to collect the specs:

// Field is ignored by json package.
Field int `json:"-"`

This one is indeed missing and can be supported easily.

// the field is omitted from the object if its value is empty,
// as defined above.
Field int `json:"myName,omitempty"`

How should this be reflected in Swagger? It should not be in the "required" list (at the moment this is not filled).

What do you mean by "Fields tagged with strings" ?

from go-restful.

Right, omitempty is a bit tricky now that you mention it.. My use case is a common Response object that is returned in all my GET methods. The response object has a couple of common fields and then specific ones that are filled depending on method. Here is an example of that object:

type Response struct {
  Code int `json:"code"`
  Users *[]User `json:"users,omitempty"`
  Items *[]Item `json:"items,omitempty"`
}

In this case I might have the resources /users and /items, and depending on resource either Users or Items will contain anything.

One idea would be to only emit the documentation listing for the field if the "template" object sent in has a instance of it (this was what I tried first myself before I realized that it didnt work at all). So if the code is like this ws.Writes(Response{Users:&[]User{}}) the user field would be included but not the items field.

However, Im not sure how to handle the case where a object is used twice (both Reads and Writes), and the template is different. (In my case this wont happen the way my code is structured)

The strings tag means that the field will be serialized as a string even if its a int or float: http://golang.org/pkg/encoding/json/#Marshal (I dont need this feature myself, but thought it would be good to handle it at the same time as the other json tags are dealt with.

from go-restful.

I created a new Issue #86 for getting support for the remaining part.

from go-restful.