Problem/Motivation

When updating a resource, it could be useful to update the related resource in the cache as well. This could prevent the display of stale data and also prevent an extra API call to the CMS.

Steps to reproduce

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Issue fork api_client-3416800

Command icon Show commands

Start within a Git clone of the project using the version control instructions.

Or, if you do not have SSH keys set up on git.drupalcode.org:

    About issue forks

    Comments

    brianperry created an issue. See original summary.

    pratik_kamble’s picture

    pratik_kamble
    Location Pune, India
    commented
    Assigned: Unassigned » pratik_kamble
    pratik_kamble’s picture

    pratik_kamble
    Location Pune, India
    commented
    Assigned: pratik_kamble » Unassigned
    brianperry’s picture

    brianperry
    he/him
    commented

    We've prioritized https://www.drupal.org/project/api_client/issues/3404988 which would provide a way to invalidate or refresh the cache. We should solve that first, and then that will likely make our options here clearer. Leaving this as postponed for now.