Skip to content
This repository has been archived by the owner on Apr 26, 2024. It is now read-only.

Determine an effective way to differentiate between internal batched event creation and batch_send batched events #14689

Open
H-Shay opened this issue Dec 16, 2022 · 0 comments
Open

Determine an effective way to differentiate between internal batched event creation and batch_send batched events #14689

H-Shay opened this issue Dec 16, 2022 · 0 comments
Labels
O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Tolerable Minor significance, cosmetic issues, low or no impact to users. T-Task Refactoring, removal, replacement, enabling or disabling functionality, other engineering tasks.

Comments

@H-Shay
Copy link
Contributor

H-Shay commented Dec 16, 2022

Per the discussion on #14575, is there an effective way to differentiate between events created for a batch internally (like when a new room is created?) and events created for MSC2716/the batch_send endpoint? The nomenclature can be confusing and we can probably do better.
@H-Shay H-Shay added S-Tolerable Minor significance, cosmetic issues, low or no impact to users. T-Task Refactoring, removal, replacement, enabling or disabling functionality, other engineering tasks. O-Uncommon Most users are unlikely to come across this or unexpected workflow labels Dec 16, 2022
@H-Shay H-Shay mentioned this issue Dec 16, 2022
Merged
@matrixbot matrixbot mentioned this issue Dec 21, 2023
Open
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
O-Uncommon Most users are unlikely to come across this or unexpected workflow S-Tolerable Minor significance, cosmetic issues, low or no impact to users. T-Task Refactoring, removal, replacement, enabling or disabling functionality, other engineering tasks.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@H-Shay