SethFalco/commandler
SethFalco/commandler
Watch
1
Code Issues 44 Pull requests Projects Releases Packages Activity Actions

Conversational Dispatcher #95

New issue
Open
opened 2020-06-04 01:24:24 +01:00 by Ghost · 0 comments
Ghost commented 2020-06-04 01:24:24 +01:00 (Migrated from codeberg.org)
Copy link

Feature Request

Description

Commandler should provide a ConversationalDispatcher, which instead of using single function commands
can follow up with a conversation with a kind of session like interaction.

Motivation

This will be useful for creating prompts like:

Are you sure you want to do this?

For example, using the StandardDispatcher once can do:
$kick Seth

The response may be:
Are you sure you want to kick Seth?

The ConversationalDispatcher can be used to listen for a yes or no, by checking the response against the ActionCache.

# Feature Request <!-- If you feel a heading is irrelevant, just leave it empty or remove it. --> ## Description <!-- Explain what this is about, try to use full sentences, and make your point clear. --> Commandler should provide a `ConversationalDispatcher`, which instead of using single function commands can follow up with a conversation with a kind of session like interaction. ## Motivation <!-- Why is this a feature that should be implemented in Commandler rather than in your own project using it? What makes this fundamental, or reusable, or of demand to other developers? --> This will be useful for creating prompts like: > Are you sure you want to do this? For example, using the `StandardDispatcher` once can do: `$kick Seth` The response may be: `Are you sure you want to kick Seth?` The `ConversationalDispatcher` can be used to listen for a `yes` or `no`, by checking the response against the `ActionCache`.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
i18n
4.0.1
Labels
Clear labels   
bug
Something that's not working as intended in an existing project's functionality.

  
feature-request
A brand new feature for an existing project.

  
upstream
Should be resolved through an upstream contribution.

No labels
bug
feature-request
upstream
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
SethFalco/commandler#95
No description provided.