handling error before .[response type]()

[neves]

First of all, awesome API!

this works wretch().get().error() but not this wretch().error().get() gives .error is not a function.

How can I setup a default error handler, before calling get/post/etc?

[elbywan]

First of all, awesome API!

Hi @neves, thanks a lot 😄!

How can I setup a default error handler, before calling get/post/etc?

To do that, you can use the catcher method.

const w = wretch()
  .catcher(404, err => redirect("/routes/notfound", err.message))
  .catcher(500, err => flashMessage("internal.server.error"))

w.url(...).get() // 404 and 500 are already taken care of

[neves]

Is there a good reason I can't use .error and others syntactic sugar like .badRequest?

[elbywan]

Is there a good reason I can't use .error and others syntactic sugar like .badRequest?

Well these helpers (notFound, badRequest…) are meant to be used after the request resolves. catcher on the other hand is meant to be used before the request has been sent.

Using the helpers before the request has been sent will just not work and throw an error (the one you posted).

[neves]

Maybe the docs need to be updated at https://github.com/elbywan/wretch#catchers or even better, add those syntactic sugar to be used before request

[elbywan]

I find it confusing to duplicate method names (catcher is "borderline" already since it is used at 2 places). And I don't want to bloat the library by adding too much extra stuff.

Also, I already linked the proper section of the documentation in my previous comment:

https://github.com/elbywan/wretch#catchererrorid-number--string-catcher-error-wretchererror-originalrequest-wretcher--void

[neves]

Are you sure? This code does not work:

// Default catchers can be overridden if needed. w.url("...").notFound(err => / overrides the default 'redirect' catcher /)

[elbywan]

This code does not work

Indeed this line has a typo thanks for pointing this out 👍 (just pushed a fix).