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

allow non-renderable async states #1

Open
ethanresnick opened this issue Nov 1, 2016 · 2 comments
Open

allow non-renderable async states #1

ethanresnick opened this issue Nov 1, 2016 · 2 comments

Comments

@ethanresnick
Copy link
Owner

ethanresnick commented Nov 1, 2016

I'm not sure what the harm is...

[this would require updating resolveBranches to call backgroundTrigger as we branch over these non-renderable states, and it would require listing AsyncState explicitly in the UsableState type if it's not already].

@ethanresnick
Copy link
Owner Author

ethanresnick commented Dec 18, 2016

It would also mean that an async state needs to be branching or renderable. Because if it's not either (i.e., if it just has backgroundTrigger()), then there's no twiml to respond to the user with when we branch to it.

So being async would become like being routable: it can be applied to either a branching state or a renderable state, but a state that's just async is invalid.

@ethanresnick
Copy link
Owner Author

Under the proposal in #7, something like this could become beforeTransitionOut...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant