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
{{ message }}
This repository has been archived by the owner on Jan 22, 2020. It is now read-only.
In a case of an error on the server side, the next middleware in chain is called without logging the error. In some cases the rendering logic silently fails and it's hard to debug rendering issues. An example would be rendering a template from an existing error middleware.
Suggested improvement: Adding a debug statement in the catch block.
The text was updated successfully, but these errors were encountered:
@slatkovic are you suggesting to add something like debuglog? A PR would be awesome. if not, will address this as soon as we get done with making react-engine compatible with react-router 1.x
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
In a case of an error on the server side, the next middleware in chain is called without logging the error. In some cases the rendering logic silently fails and it's hard to debug rendering issues. An example would be rendering a template from an existing error middleware.
Suggested improvement: Adding a debug statement in the catch block.
The text was updated successfully, but these errors were encountered: