You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Providing a built-in, configurable client-side helper (e.g. allowing behaviours such as automatic throwing on serverError) would reduce boilerplate and encourage a consistent, ergonomic error-handling pattern across client code.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
When consuming
next-safe-actionresults on the client, it is common to repeat the same pattern:This pattern is especially frequent when integrating with libraries such as:
To avoid repetition, many users end up creating a small utility like:
Providing a built-in, configurable client-side helper (e.g. allowing behaviours such as automatic throwing on
serverError) would reduce boilerplate and encourage a consistent, ergonomic error-handling pattern across client code.Beta Was this translation helpful? Give feedback.
All reactions