Channel: Allow non-identical sent vs. received events #2164
Description
Use Case
It can happen that the sent event and the received (read) event are similar in content, but not identical. For example, some services do not include optional fields. I want to represent this scenario in MDX files, but at the moment it can’t be modeled in a meaningful way.
Would it be possible to extend it accordingly?
Proposed Solution
No response
Implementation Notes
No response
Community Notes
- Please vote by adding a 👍 reaction to the issue to help us prioritize.
- If you are interested to work on this issue, please leave a comment.
- If this issue is labeled needs-discussion, it means the spec has not been finalized yet. Please reach out in the EventCatalog Discord.