Allow action to throw error

[qiushiyan]

It would be convenient to add a helper chaining method (e.g. .throw()) so that the server action would throw the error instead of returning it.

Use cases: the error.tsx and <ErrorBoundary /> components would automatically work if the server action throws the error, now I have to manually re-throw it

// page.tsx
const [data, err] = await action()
if (err) {
 throw new Error(err)
}

if with the chaining method I could just do

const action2 = action.throw()
const data = await action2()

[IdoPesok]

Hi, I am planning to improve error handling for the 1.0.0 release. Will make sure this functionality is available. In the meantime, you can try throwing the error in the shape error function on a base procedure.

[qiushiyan]

Thanks for the amazing work!

[JoshuaKirby88]

Hey, I'm not really familiar with what errors can be.
In the experimental_shapeError callback, err is of type "unknown", whereas I thought all errors from zsa are of type TZSAError.
Can errors from experimental_shapeError be both an instance of the Error class, as well as TZSA?

"use server"

import { createServerActionProcedure, TAnyCompleteProcedure } from "zsa"

export const DALProcedure = (procedure: TAnyCompleteProcedure) => {
    return createServerActionProcedure(procedure)
        .experimental_shapeError(({ err }) => {
            const error = typeof err === "object" && err !== null && "data" in err && typeof err.data === "string" ? err.data : "Unknown database error"
            throw new Error(error)
        })
        .handler(() => {})
}

[Kamahl19]

@IdoPesok Hey, just wondering are you still working on this project or do you still plan to release v1? Anyway thanks for the great work.

[JoshuaKirby88]

@Kamahl19

I tried creating my own helper function for creating server actions and handling server action results and it's quite good since you can add a lot of custom behaviours like:

• Instrument server action with Sentry (recording input and output).
• Capture exception to Sentry on input parse error.
• Automatically load i18n translations for the server action by passing the name of the server action.
• Handling auth procedures.
• Catching all errors and reporting to Sentry with the input, name of server action and auth procedure result.

And a function to handle the result on the client that:

• Determines if the server action errored.
• Render a toast automatically on error.

Let me know if you're interested.