When customers call our JSON:API API, they can use an "include" parameter
to specify related objects to be appended to the response.
However, requests to include are not always satisfiable (e.g. if
job.supervisor=null, include=supervisor is ignored).
In order to prevent Marshmallow from trying
re how this API_Person class is useful because you can't
> query for them. I would think that if you cant change the original
> model then you'd have this API_Person as a series of helper functions that
> accept a Person as their argument.
>
>
>
> On Wed, Sep 6, 2023, at 1:56
The project I am working on is split up into several modules. Previously,
each module had its own ORM classes.
However, due to several bugs arising from forgetting to update each
module's ORM classes in lock step when adding new functionality, we have
decided it would be best to extract the ORM
