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
Currently when error throws we present it in a "new page" which replaces user's current UI (for example: a login page), or in an outlet. But in many scenarios we don't want to leave the current page to display error information, for example, in login case we normally show the login error just below the loign button, or maybe a modal dialog. The default error rendering in my opinion is not user friendly . Is there anyway to have other rendering options? I have tried outlet but it's either too much work or impossible for this requirement. Note this is dealing with the errors come from the backend server, not the validation in frontend.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Currently when error throws we present it in a "new page" which replaces user's current UI (for example: a login page), or in an outlet. But in many scenarios we don't want to leave the current page to display error information, for example, in login case we normally show the login error just below the loign button, or maybe a modal dialog. The default error rendering in my opinion is not user friendly . Is there anyway to have other rendering options? I have tried outlet but it's either too much work or impossible for this requirement. Note this is dealing with the errors come from the backend server, not the validation in frontend.
Beta Was this translation helpful? Give feedback.
All reactions