Skip to content

Do not cache includes on create/update #78

@zeitlerc

Description

@zeitlerc

When JSON API responds with updated relationship information, it does not include the full resource. This causes out-of-date or missing Meta attributes on resources that were created as includes on the operation. When a model is created or updated with includes, the included models should not be cached and the relationship should be forced to be re-fetched.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions