Skip to content

chore: warn when loadCdn is used on the experimental backend#295

Open
mfazekas wants to merge 1 commit into
feat/rive-ios-experimentalfrom
chore/warn-loadcdn-experimental
Open

chore: warn when loadCdn is used on the experimental backend#295
mfazekas wants to merge 1 commit into
feat/rive-ios-experimentalfrom
chore/warn-loadcdn-experimental

Conversation

@mfazekas

@mfazekas mfazekas commented Jun 17, 2026

Copy link
Copy Markdown
Collaborator

loadCdn is silently ignored on the experimental backend (its CommandQueue file-load API has no CDN asset resolution). This makes loadCdn optional and adds a one-time console.warn only when a caller explicitly passes loadCdn: true on that backend, pointing them to referencedAssets; the common case (no loadCdn, e.g. useRiveFile) is unaffected. Context: #15.

@mfazekas mfazekas force-pushed the chore/warn-loadcdn-experimental branch from a64bb86 to 2f7bb20 Compare June 17, 2026 07:44
The experimental backend ignores `loadCdn` — its CommandQueue file-load API
(`RiveFile.fromSource(source, worker)`) has no CDN asset resolution, so the
`loadCdn` argument on `RiveFileFactory.from*` is silently a no-op there.

`loadCdn` is now optional (the effective default of `true` is applied only at
the native call via `?? true`), and a one-time `console.warn` is emitted only
when a caller *explicitly* passes `loadCdn: true` while on the experimental
backend — so the common case (not passing `loadCdn`, e.g. `useRiveFile`) is
never warned. JSDoc updated to note the option is ignored on experimental.
@mfazekas mfazekas force-pushed the chore/warn-loadcdn-experimental branch from 2f7bb20 to e3e16ff Compare June 17, 2026 07:52
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.

1 participant