-
Notifications
You must be signed in to change notification settings - Fork 87
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[fature idea] Hook: withCustomError #569
Comments
That would definitely be useful if an error needs to be, for example, localized. |
+1 |
For the record, in case anyone else copies this, an await is required before the call to the internal hook. const withCustomError = (hook, errorCreator) => (context: any) => {
try {
// if the hook does not produce an error, no need to throw
const res = await hook(context);
return res;
} catch (err) {
throw errorCreator(context);
}
}; |
Thanks for the suggestion and sorry for the late response. I started working on a massive rewrite of the package (#764). It's not released yet and will take a few weeks. This should be working then. I took a more drastical approach. I introduced a new hook called |
Hello guys,
I'm submitting the basic idea here and once you approve it, I'll add the PR with types and tests et al.
The hook is called
withCustomError
and it can be used to change errors thrown by other hooks.The scenario goes like this: I want to use the
disable
hook but return a 404 NotFound error instead of the default MethodNotAllowed error.Basically, instead of writing the following e.g:
We would wrap it in a
withCustomError
utility hook, like so:The basic code goes like this:
We can also use function composition to create a new
disallow404
like so:What do you think ?
The text was updated successfully, but these errors were encountered: