[PB-5858]: Properly propagate product changes on proper event on websocket#243
Open
AlexisMora wants to merge 2 commits intomainfrom
Open
[PB-5858]: Properly propagate product changes on proper event on websocket#243AlexisMora wants to merge 2 commits intomainfrom
AlexisMora wants to merge 2 commits intomainfrom
Conversation
|
egalvis27
approved these changes
Feb 12, 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.
What is Changed / Added
Now, we only check for products once at startup, and once the event 'PLAN_UPDATED' is recieved from websockets,
and event then, we only propagate the changes to the renderer proces only if the new, retrieved object is different from the one we already have stored.
Why
This way we reduce drastically the amount of requests we do for user product availability