Same resources with different attributes in different objects

4

Hey,
that product relation seems like a m:n relation with pivot data, right?

Shippings-Table {shipping_id, …}
Products-Table {shipping_id, part_id, qtyShipped, other-pivot-data}
Parts-Table {part_id}

I didn’t like it to put on the meta-tag, because actually its not meta-information.
I’ve added the field “pivot” (outside of the specification)

"included": [
    {
      "type": "parts",
      "id": "10PIQPD3",
      "attributes": {
           "name": "Part PIQ PD3", ...
      },
      "pivot": {
          "partCondition": "F01",
          "qtyShipped": 1
      }, 
      links: { self: '/parts/10PIQPD3?shipping_id=1' }
    }
]

As well I populate the links with params, like here linking to an ID: shipping_id

But actually while writing I’ve checked the specification, and I don’t know whether its good to do that?

Sorry, I think that was not to much help, but maybe it helps you for your project.