-
Notifications
You must be signed in to change notification settings - Fork 9
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add pop up message on the UI when backend fail #62
Labels
Comments
yeah something like that. I agree that error dialog windows will be our preferable ways of showing the error. Anyway, when did you get this error? |
Yeah, sorry the word popup has the connotation of dialog but I didn't mean
that. Just some absolute positioned, user dismissable thing that doesn't
break control flow but at least gives some feedback that the thing the user
asked for didn't work. Way better to have a token notification area than
things just silently failing one day.
Like what is standard in bootstrap:
https://getbootstrap.com/docs/4.0/components/alerts/
…On Wed., 12 Jun. 2019, 18:47 Herbert Valerio Riedel, < ***@***.***> wrote:
I'm not sure what you mean by "error popup" but I consider "error dialog
windows" rather annoying. I'd hope to have something like e.g. GitHub does
when a webservice fails by showing a "banner" at the top which you can
close by pressing the x button, e.g.
[image: youcantperform]
<https://user-images.githubusercontent.com/285533/59336751-6fb20e80-8cff-11e9-8bae-27d0d9ddfbf7.png>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#62?email_source=notifications&email_token=AABG3XMFCI5M7XHPDAHNXH3P2CZZTA5CNFSM4HW23TMKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXPWKDA#issuecomment-501179660>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AABG3XJRSKHQHU6QUYUPGJDP2CZZTANCNFSM4HW23TMA>
.
|
@benkolera noted Ben, thank you. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When working on this #58, There is a discussion on how we handle the UI when the backend fail.
@benkolera mentioned that "you should consider having a way to print the errors out somewhere on the backend failure cases. A EventWriter with an error message to some global error popup can work well."
The text was updated successfully, but these errors were encountered: