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.

Sign up for GitHub

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

Jump to bottom

Decide on a standard response for no-action-found #19

Open
eharpste opened this issue Oct 25, 2016 · 0 comments
Open

Decide on a standard response for no-action-found #19

eharpste opened this issue Oct 25, 2016 · 0 comments
Labels
API Usability Issues related to making the system easier to use on a software level Authoring Issues related to "end-user" authoring Refactoring Stuff that makes things easier for us
Projects
Apprentice Learner Road Map

Comments

@eharpste
Copy link
Member

Currently the agent API is de facto defined by the behavior of the LogicalWhereWhenHow learner. One aspect of this is when no action is found on a request it just returns an empty dictionary. It might be good to define a common behavioral style to denote that no action was found rather than just returning an empty set. Maybe something like {"no_action":True} or something simple.
@eharpste eharpste added enhancement Refactoring Stuff that makes things easier for us labels Oct 25, 2016
@eharpste eharpste added this to Non-Essential To Do in Apprentice Learner Road Map Apr 5, 2019
@eharpste eharpste added API Usability Issues related to making the system easier to use on a software level Authoring Issues related to "end-user" authoring and removed enhancement labels Apr 8, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
API Usability Issues related to making the system easier to use on a software level Authoring Issues related to "end-user" authoring Refactoring Stuff that makes things easier for us
Projects
No open projects
Apprentice Learner Road Map
  
Back Burner
Milestone
No milestone
Development

No branches or pull requests
1 participant
@eharpste