Skip to content

feat(cacheable): support tag invalidation in getOrSet - #1695

Open
laesse wants to merge 4 commits into
jaredwray:mainfrom
laesse:feature/tags-for-getOrSet
Open

feat(cacheable): support tag invalidation in getOrSet#1695
laesse wants to merge 4 commits into
jaredwray:mainfrom
laesse:feature/tags-for-getOrSet

Conversation

@laesse

@laesse laesse commented Aug 7, 2026

Copy link
Copy Markdown

Add tags to GetOrSetFunctionOptions and forward them to set when a value is computed on a cache miss. Add regression coverage and update the documentation with tag-based getOrSet usage.

Please check if the PR fulfills these requirements

  • Followed the Contributing guidelines and Code of Conduct
  • Tests for the changes have been added (for bug fixes/features) with 100% code coverage.

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

laesse and others added 2 commits July 30, 2026 15:05
Add tags to GetOrSetFunctionOptions and forward them to set when a
value is computed on a cache miss. Add regression coverage and update
the documentation with tag-based getOrSet usage.
@codecov

codecov Bot commented Aug 26, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (1af5c5c) to head (e80fce1).

Additional details and impacted files
@@            Coverage Diff            @@
##              main     #1695   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           29        29           
  Lines         3513      3513           
  Branches       809       809           
=========================================
  Hits          3513      3513           

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@jaredwray

Copy link
Copy Markdown
Owner

@laesse - thanks for your patience as I had to do some work on this repo before adding more features

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants