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.

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

Removed unused docs/README.md #30

Merged
merged 2 commits into from
Dec 5, 2024
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -38,7 +38,7 @@ Whenever Magento writes to the databse, it triggers a `model_save_commit_after`
event. This module attaches an event listener to that event and publishes
messages to a rabbitmq queue if that event is configured/whitelisted.

![Webhooks flow](docs/Webhooks.png "Webhooks flow")
![Webhooks flow](Webhooks.png "Webhooks flow")

A consumer then reads from the queue and loads the subscribers to that event
and dispatches a 'notification'.
Expand Down Expand Up @@ -273,4 +273,4 @@ But then we are leaking an implementation detail. Perhaps `metadata` could be an

Or we could update metadata using a `PUT` endpoint when we decide that a specific webhook needs a specific notifier.

Or we could build some functionality in the admin UI and allow to edit and choose from a dropdown for available notifiers.
Or we could build some functionality in the admin UI and allow to edit and choose from a dropdown for available notifiers.