This repository was archived by the owner on Sep 4, 2025. It is now read-only.
Repository navigation
This repository was archived by the owner on Sep 4, 2025. It is now read-only.
Unmarshal access to "meta" #82
Description
It'd be great to have access to an annotation type "meta" or some other way to easily access the Meta information from a JSON API document.
Currently I'm unmarshaling twice: once into OnePayload via encoding/json and again via the jsonapi unmarshal methods. It'd be wonderful to button this up.
Activity
svperfecta commentedon Apr 11, 2017
The point of meta is to describe the response.. What's the point of submitting a request with meta to your api? If its a required field, it should be in attributes or another object? Not disagreeing, just wondering what the use-case is?
mitchellh commentedon Apr 11, 2017
My use case is actually for a response, I'd like to extract that meta result. Currently I'm unmarshaling twice to get it since the tags don't support getting it directly.
svperfecta commentedon Apr 12, 2017
tscott0 commentedon Nov 21, 2018
Hi there. Is there any update on this issue or the related #95 ?
My use-case requires creating a go JSON API server and client, meaning I will need to marshal and unmarshal the data. More specifically, I would like access to the "meta" for a relationship, which seems to be already supported for marshalling (see https://github.com/google/jsonapi/blob/master/node.go#L59).
My current options seem to be:
encoding/json.If anyone has any other potential workarounds, I'd be extremely grateful!
nikhilatshaw commentedon Dec 29, 2020
func setDataIntoTarget(data *Data, target interface{}) error {} is missing following chunk of code which will resolve meta part of unmarshaling
if data.Meta != nil {
err = json.Unmarshal(data.Meta, castedTarget)
if err != nil {
return err
}
}