Someone gets on an error page. Instead of being all confused what happened, he'll now only be slightly confused of what just happened, since things will at least look like they belong to the page.
Environment
Browser:
[ ] Chrome (desktop) version:
[ ] Chrome (Android) version:
[ ] Chrome (iOS) version:
[ ] Firefox version:
[ ] Safari (desktop) version:
[ ] Safari (iOS) version:
[ ] IE version:
[ ] Edge version:
For development issues:
Node version:
Operating System:
Additional Description
Implementing this is probably easiest through cubic-api middleware functions that hijack the res object and check if the statusCode is >= 400. I'd suggest simply going with one generic template. Things will take too much time otherwise.
I'm submitting a...
Current behavior
Error pages return the raw cubic error responses.
Expected behavior
Should return a proper styled error page.
Minimal reproduction of the problem
Someone gets on an error page. Instead of being all confused what happened, he'll now only be slightly confused of what just happened, since things will at least look like they belong to the page.
Environment
Browser:
For development issues:
Additional Description
Implementing this is probably easiest through cubic-api middleware functions that hijack the
res
object and check if the statusCode is >= 400. I'd suggest simply going with one generic template. Things will take too much time otherwise.