Lack of descriptive guard errors #33

New Issue

Jef Roosens · 2021-09-01T16:44:37+02:00

Jef Roosens commented

2021-09-01 16:44:37 +02:00

Currently, request guards can only return a status code which can then be handled by a default catcher. There's no option to return custom response content, so any guard errors are automatically turned into generic response. This is just sad man, I really hope they implement this.

It seems I'm not the only one with this issue, so it's being tracked here.

Currently, request guards can only return a status code which can then be handled by a default catcher. There's no option to return custom response content, so any guard errors are automatically turned into generic response. This is just sad man, I really hope they implement this. It seems I'm not the only one with this issue, so it's being tracked [here](https://github.com/SergioBenitez/Rocket/issues/749).

Jef Roosens added the

bug

Backend

labels 2021-09-01 16:44:38 +02:00

Jef Roosens added the

Upstream

label 2021-09-04 19:08:46 +02:00

This repo is archived. You cannot comment on issues.