Skip to content

fix(react-headless): cacheQueryResults can be passed to useOpenuiCloudStorage and OpenUICloudProvider - #1627

Merged
Aditya-thesys merged 1 commit into
mainfrom
ap/cache-opt-out
Nov 12, 2026
Merged

Aditya-thesys merged 1 commit into
mainfrom
ap/cache-opt-out

Conversation

@Aditya-thesys

Copy link
Copy Markdown
Contributor

What

0.18.7 added showing a dashboard's last results while it reloads, and its release note said cacheQueryResults: false turns it off. That option could not be passed: it lives on cloudArtifactStorage, which is not exported, and useOpenuiCloudStorage and OpenUICloudProvider built the storage without it.

This adds cacheQueryResults?: boolean (default true) to OpenuiCloudOptions and passes it through. OpenUICloudProvider takes the same options, so it accepts it too.

<OpenUICloudProvider token="/api/frontend-token" cacheQueryResults={false}>

With false, the artifact storage has no getQueryResults / putQueryResult, so the renderer makes no query-results request and passes every call straight through.

Checked

  • New test: both methods are present by default and absent with cacheQueryResults: false; the rest of the artifact storage is unchanged.
  • react-headless cloud tests (47) pass; typecheck and lint are clean for react-headless, typecheck for react-ui.

🤖 Generated with Claude Code

@vercel

vercel Bot commented Nov 12, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
openui-docs Ready Ready Preview Nov 12, 2026 4:26pm UTC

Request Review

@Aditya-thesys
Aditya-thesys merged commit d3763f5 into main Nov 12, 2026
4 checks passed
@Aditya-thesys
Aditya-thesys deleted the ap/cache-opt-out branch November 12, 2026 16:36

This branch was successfully deployed

1 active deployment
Preview — 21c5625c Deployed Nov 12, 2026 by vercel[bot]
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