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

Reusing AsyncAdapter #9

Open
kalexmills opened this issue May 10, 2023 · 0 comments
Open

Reusing AsyncAdapter #9

kalexmills opened this issue May 10, 2023 · 0 comments

Comments

@kalexmills
Copy link
Collaborator

kalexmills commented May 10, 2023

This might not be an issue, I could just think that I'm doing a hack when everything is working as designed.

There are a very few circumstances where I need to abort dialogue entirely and send a customer on their way. The best way I've found to do this using the brand spanking new AsyncAdapter is to use Abort. When I do so, AsyncAdapter transitions to a terminal state, so I have to create a new one to re-use the same VM. (In my games, we compile everything to a single yarn file and run different nodes based on.... logic.)

I can definitely do that and it works, but I'm filing an issue in case this is an edge-case in the design / API. Please close if this is working as intended. :)

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