-
Notifications
You must be signed in to change notification settings - Fork 965
Implement Realtime Autofetch on Config Update Notifications #9206
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Implement Realtime Autofetch on Config Update Notifications #9206
Conversation
🦋 Changeset detectedLatest commit: 5d43520 The changes in this PR will be included in the next version bump. This PR includes changesets to release 4 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Size Report 1Affected Products
Test Logs |
Size Analysis Report 1Affected Products
Test Logs |
53d07fd
to
c4a8b72
Compare
…eAndBeginRealtimeHttpStream`, removing await from the front of the beginRealtime.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, pls ensure to add tests in a follow-up PR (if not being done in this one).
Yes, tests are added in: #9210 |
Added unit test cases.
This PR is a follow-up to #9202.
This PR adds logic to listen for realtime update notifications. When a new template version is detected, it automatically fetches the config. After a successful fetch, a callback is triggered to notify the app that a new config version has been retrieved and is ready to be activated.
Next PR will include test cases for all the functionalities.