Skip to content

Added After event processed#28

Draft
daehli wants to merge 1 commit intomainfrom
feature/after-event-processed
Draft

Added After event processed#28
daehli wants to merge 1 commit intomainfrom
feature/after-event-processed

Conversation

@daehli
Copy link
Copy Markdown
Contributor

@daehli daehli commented Apr 4, 2022

Describe the event process, related to #25

@Gordon-BP

@vercel
Copy link
Copy Markdown

vercel bot commented Apr 4, 2022

This pull request is being automatically deployed with Vercel (learn more).
To see the status of your deployment, click below or on the icon next to each commit.

🔍 Inspect: https://vercel.com/botpress-team/documentation/J2FYzvF3pqsXvB7Yvb3y5UZ8UgHQ
✅ Preview: https://documentation-git-feature-after-event-processed-botpress-team.vercel.app

@daehli daehli requested a review from ptrckbp April 4, 2022 14:25
@Gordon-BP
Copy link
Copy Markdown

What's a good use case for after_event_processed hooks? How are they different from after_incoming_middleware?

@daehli
Copy link
Copy Markdown
Contributor Author

daehli commented Apr 4, 2022

An event (Message/payload/content-type) can have multiple middleware(basic-skills/05_extract_slots.js,builtin/apply_nlu_contexts.js). Those middlewares can affect the event. The after_incoming_middleware will modify every middleware.

The after_event_processed is processed only one time at the end end of the event pipeline.

I don't have any good use case or any idea for the moment.

@daehli daehli marked this pull request as draft April 11, 2022 17:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants