Field Values that are Ecto Embedded Structs or Embedded Lists
Right now we don't explicitly support Ecto Embedded schemas, if you manually do functions you can strip away the Struct meta data and embed the raw map.
JSON API does allow for any json type including lists or objects.
Since these embedded data structures typically don't have IDs and are not typically query-able as resources they should not be included as relationships.
We could make this easier by recognizing that the field is a struct and pulling out non-struct fields with Map.from_struct and structs from lists.
This issue has been automatically marked as "stale:discard". We are sorry that we haven't been able to prioritize it yet. If this issue still relevant, please leave any comment if you have any new additional information that helps to solve this issue. We encourage you to create a pull request, if you can. We are happy to help you with that.
Closing this issue after a prolonged period of inactivity. If this issue is still relevant, feel free to re-open the issue. Thank you!