New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

What about types implement json.Marshaler or interfaces ? #3

Open

ferhatelmas opened this issue Apr 11, 2017 · 0 comments

ferhatelmas commented Apr 11, 2017 •

edited

Loading

Let's say we have custom time which outputs Unix timestamp when serialized but generated spec will be verbose with every field in our time.

"date": {
  "Time": {
    "loc": {
      "cacheEnd": 0,
      "cacheStart": 0,
      "cacheZone": {
      "isDST": true,
      "name": "string",
      "offset": 0
    },
    ...
  },
}

What I expect is { "date": 0 }. What do you advise to handle these types ?
Corollary, handlers that return interfaces are also an issue ?

Anyway, thanks, it helped me a lot.

The text was updated successfully, but these errors were encountered:

bjyoungblood mentioned this issue

Allow custom type registration #9

Closed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment