feat: add block participants updates #35
Open
Conversation
This file contains 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
|
The preview deployment is ready. 🟢 Open Preview | Open Build Logs Last updated at: 2024-12-03 17:23:27 CET |
|
gpt driven opis pr'ki, grubo |
Rei-x
requested changes
Dec 4, 2024
Comment on lines
+71
to
+73
| refetchOnWindowFocus: true, | ||
| refetchOnReconnect: true, | ||
| refetchOnMount: true, |
There was a problem hiding this comment.
ale wiesz że to nic nie zmienia bo by default tak jest?
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.
Intro
The participant list in blocks did not refresh after a participant registered. After conducting an in-depth analysis, I discovered that participant data in blocks is not refreshed at all. This is a critical functionality since users need real-time updates to confirm whether someone else has already taken their place in real life.
Changes
I've added all the prefetch parameters I could change. By default, places are refreshed every second using a pooling methodology. This also happens after the window focus changes, after reconnecting, and on mounting. This ensures a smooth experience.
Future development
I also noticed that the whole event (meaning configuration I guess) is also refreshed every second. This produces quite a lot of requests and we should ask ourselves how we can optimize it.