feat: broadcast storage - #2022
Draft
leandrocp wants to merge 7 commits into
Draft
Conversation
Contributor
CRAP Score Report |
leandrocp
force-pushed
the
feat-broadcast-storage
branch
from
July 30, 2026 15:05
1d562f6 to
6401d83
Compare
leandrocp
force-pushed
the
feat-broadcast-storage
branch
from
July 30, 2026 15:15
6401d83 to
4927967
Compare
leandrocp
marked this pull request as draft
July 30, 2026 15:19
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What kind of change does this PR introduce?
Introduce Broadcast Storage allowing users to opt-in message storing on broadcast via WS/Rest and client libs.