This repository was archived by the owner on Oct 9, 2025. It is now read-only.
feat(network-message): Use redis entirely to store messages #161
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.



This commit improves the handling of referenced messages in the network message
commands. The changes include:
getOriginalMessageandfindOriginalMessagefunctions to fetch theoriginal message data, handling both original and broadcast messages.
additional database queries.
fetchHubfunction to retrieve the hub data, ensuring it isavailable.
DeleteMessagecommand to use thebroadcastsproperty of theoriginal message instead of the
broadcastMsgsproperty.NetworkReactionInteractionclass to use the original messagedata directly, instead of relying on the
broadcastedMessagestable.The goal of these changes is to improve the efficiency and reliability of the
network message handling, reducing database queries and ensuring consistent
data access.