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

Introduce interface for ExplorationProgressController #122

Closed
BenHenning opened this issue Sep 17, 2019 · 1 comment
Closed

Introduce interface for ExplorationProgressController #122

BenHenning opened this issue Sep 17, 2019 · 1 comment
Labels
Priority: Essential This work item must be completed for its milestone. Z-ibt Temporary label for Ben to keep track of issues he's triaged.

Comments

@BenHenning
Copy link
Member

This is tracking introducing a stubbed interface for #115 without the real implementation being complete.

@BenHenning BenHenning added this to the Prototype -- Infra milestone Sep 17, 2019
@BenHenning BenHenning added Where: Infrastructure Priority: Essential This work item must be completed for its milestone. labels Sep 17, 2019
vinitamurthi added a commit that referenced this issue Sep 21, 2019
* New proto for explorations

* Convert any protos to a particular value

* Add new line to EOF in subtitled_html.proto

* Review changes

* Lint fix for the comment

* Change customization args for interactions and param changes

* Updated interaction objects to support the ones for the android app alone + review fixes

* Added comments for some of the objects

* Review fixes

* Removed ObjectType enum
@BenHenning BenHenning self-assigned this Sep 22, 2019
@BenHenning
Copy link
Member Author

BenHenning commented Sep 25, 2019

This is going to be modeled to eventually support ML answer classification, and for multiple routing flows (state/exploration/concept card) depending on the outcome of the answer provided.

Not all of this will be functionally implemented for the prototype, but the interface needs to consider these future cases. It's also not clear how non-state continuation will work yet. Current assumptions:

  • State continuation is regular in-controller routing
  • Exploration continuation doesn't exist; you need to restart the current exploration
  • Concept card continuation is done with the regular continueToNextState() flow

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Priority: Essential This work item must be completed for its milestone. Z-ibt Temporary label for Ben to keep track of issues he's triaged.
Development

No branches or pull requests

1 participant