Skip to content

[doc] Add explanations for built-in actions #653

@wenjin272

Description

@wenjin272

Search before asking

  • I searched in the issues and found nothing similar.

Description

Currently, when demonstrating how to declare a Workflow, our examples define two actions:

  1. Accept an InputEvent and send a ChatRequestEvent
  2. Receive a ChatResponseEvent and send an OutputEvent

Users might wonder why there’s no need to explicitly define an action that processes the ChatRequestEvent and sends the ChatResponseEvent. 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?

  • I'm willing to submit a PR!

Metadata

Metadata

Assignees

No one assigned

    Labels

    fixVersion/0.3.0The feature or bug should be implemented/fixed in the 0.3.0 version.priority/majorDefault priority of the PR or issue.tech debt[Issue Type] User-unaware issues, such as code refactor and infrastructure maintenance.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions