I have a setup where we are using a ManyToMany field with a through model, similar to the situation described in this forum post from the json-api spec .

It seems like there are two ways of approaching this. One would be to use the meta key in the relationship, such as:

{
 "type": "objective",
 "id": "00559422-02E7-11DB-8468-BA18C3C820AE",
 "relationships": {
 "concepts": {
 "data": [
 { "type": "concept", "id": "02B7", "meta": { "emphasis": "primary" } },
 { "type": "concept", "id": "3AF6", "meta": { "emphasis": "secondary" } },
 { "type": "concept", "id": "CB23", "meta": { "emphasis": "tertiary" } }
 ]
 }
 }
}

Is this possible in using this library?

On the other hand, I could have the relationship point to the through model, which would be formatted as such:

{
 "type": "ObjectiveConceptLink", 
 "id": "....", 
 "attributes": {
 "emphasis": "primary", 
 }, 
 "relationships": {
 "concept": {
 "data": {
 "type": "concept", 
 "id": "...."
 }
 }, 
 "objective": {
 "data": {
 "type": "objective", 
 "id": "...."
 }
 }
 }
}

Right now in my app, the response does not respect the through key when using a ResourceRelatedField. The resulting response relationships key has a type of objective, as opposed to objective-concept-link.

Are either of these solutions possible with this library? If so, how?