store response_events optimally
Open
- Dominant language
- Go
- Stars
- 8
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
Currently the same response event is stored once per subscription if the response event is being listened to by multiple subscriptions. Have to optimize this somehow.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.