feat: Push current sticky state when widgets wants to read sticky events#161
Merged
feat: Push current sticky state when widgets wants to read sticky events#161
Conversation
5 tasks
4 tasks
toger5
reviewed
Jan 27, 2026
|
toger5
approved these changes
Jan 29, 2026
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
2 participants
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.
Adds a new action to the widget that allows to push the current sticky statePush all the sticky events using the existing send event action when a widget is requiring the capability to read sticky eventsIf this is not done, the widget will only have a partial view of the current "sticky map" and will miss important info.
This also means that the widget is getting access to past messages (up to 1h old - the max sticky duration).