Skip to content

feat: tag based invalidation - #124

Open
code-forger wants to merge 3 commits into
feat/rsc-persistent-cachefrom
feat/rsc-persistent-cache-tags
Open

code-forger wants to merge 3 commits into
feat/rsc-persistent-cachefrom
feat/rsc-persistent-cache-tags

Conversation

@code-forger

Copy link
Copy Markdown
Member

Description

Support tag based invalidation

Motivation and Context

During a server actions, you might not be able to full reconstruct the cache key for cached data, instead you can invalidate entries by tag.

Additionally, you might want to invalidate large amounts of the cache at a time, like an entire product catalogue, or all data relating to a single user. Tags also allow you to do this.

How Has This Been Tested?

unit tests

Types of Changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation (adding or updating documentation)
  • Dependency update

Checklist:

  • My change requires a change to the documentation and I have updated the documentation accordingly.
  • My changes are in sync with the code style of this project.
  • There aren't any other open Pull Requests for the same issue/update.
  • These changes should be applied to a maintenance branch.
  • I have added the Apache 2.0 license header to any new files created.

What is the Impact to Developers Using Fetchye?

@code-forger
code-forger added this pull request to stack #123 September 26, 2026 14:34
@code-forger
code-forger requested review from a team as code owners September 26, 2026 14:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant