Repository navigation
feat(pages): export isVoidActionError() to recognize action errors at every status - #715
Merged
cpojer merged 1 commit intoNov 4, 2026
Conversation
… every status Closes voidzero-dev#714 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fixes #714
Problem
The actions guide says
401,403and5xxaction errors are thrown, and to handle them with an error boundary. The only exported guard,isCallSiteActionError(), isfalsefor exactly those statuses. An app has to checkerror.name === 'VoidActionError'by hand to tell a failed action from a render bug, becauseinstanceofisn't reliable when the class is bundled more than once.Change
isVoidActionError(error)istruefor aVoidActionErrorat any status and narrows the type. It checks the name and a numericstatus, like the existing guard.isCallSiteActionError()now callsisVoidActionError()and keeps its behavior.VoidActionErrortype are exported fromvoid/pages-clientand from@void/react,@void/vue,@void/svelteand@void/solid. The guide already importsactionfrom the adapter packages, so the guards are available from the same place.action()isVoidActionError()isCallSiteActionError()truetruetruefalsetruefalsetruefalseDocs
401and a403withisVoidActionError(), and a sentence onisCallSiteActionError().Tests
packages/void/test/unit/action-result.test.ts:isVoidActionError()istruefor401,403,409,422and500, and for a structurally equivalent object from another bundled copy.falsefor a plainError, a missing or non-numericstatus,null, and a string.isCallSiteActionError()istruefor409and422, andfalsefor401,403,500and a plainError.Verification
On Node 24.22.1 (
.node-version):🤖 Generated with Claude Code