-
Notifications
You must be signed in to change notification settings - Fork 119
[doc] Add explanations for built-in actions #653
Copy link
Copy link
Open
Labels
fixVersion/0.3.0The feature or bug should be implemented/fixed in the 0.3.0 version.The feature or bug should be implemented/fixed in the 0.3.0 version.priority/majorDefault priority of the PR or issue.Default priority of the PR or issue.tech debt[Issue Type] User-unaware issues, such as code refactor and infrastructure maintenance.[Issue Type] User-unaware issues, such as code refactor and infrastructure maintenance.
Metadata
Metadata
Assignees
Labels
fixVersion/0.3.0The feature or bug should be implemented/fixed in the 0.3.0 version.The feature or bug should be implemented/fixed in the 0.3.0 version.priority/majorDefault priority of the PR or issue.Default priority of the PR or issue.tech debt[Issue Type] User-unaware issues, such as code refactor and infrastructure maintenance.[Issue Type] User-unaware issues, such as code refactor and infrastructure maintenance.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Search before asking
Description
Currently, when demonstrating how to declare a Workflow, our examples define two actions:
InputEventand send aChatRequestEventChatResponseEventand send anOutputEventUsers might wonder why there’s no need to explicitly define an action that processes the
ChatRequestEventand sends theChatResponseEvent. This is because the framework provides a built-in chat action that handles this automatically. However, we currently have no explanation here, which may confuse users.Are you willing to submit a PR?