Skip to content
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

Server asynchronous notifications channel #254

Closed
jordanh opened this issue Aug 28, 2016 · 1 comment
Closed

Server asynchronous notifications channel #254

jordanh opened this issue Aug 28, 2016 · 1 comment
Milestone

Comments

@jordanh
Copy link
Contributor

jordanh commented Aug 28, 2016

Issue - Enhancement

We'd like to background some longer running requests, such as #221. The way it's presently written, we get to the end of the process and then return errors.

Errors don't always have to be synchronous. We could let the user know later that a recoverable error happened. JTBD would read like:

  • When a user invites their teammates and mistypes and email, they want to know sometime that the email address was incorrect (and be given a link to a process for how to fix it), so that they can onboard their entire team

We could subscribe an outer container to a feed that could pop toasts from the server. That way, long running tasks could be given callbacks which use this channel when things go wrong (or, things go right!)

@jordanh
Copy link
Contributor Author

jordanh commented Jan 11, 2017

No need driving this at the moment.

@jordanh jordanh closed this as completed Jan 11, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant