You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It appears that the current implementation of the competitions live data listener is using that of the competitions-lobby page, meaning all competitions changes of type: published are registered and sent to the frontend. This consumes unnecessary resources and bandwidth.
Is there an existing issue for this?
🐞 Describe the bug
It appears that the current implementation of the
competitions
live datalistener
is using that of thecompetitions-lobby
page, meaning all competitions changes oftype: published
are registered and sent to the frontend. This consumes unnecessary resources and bandwidth.🤔 Expected Behavior
Limit to one single
competition-id
listen forlive
data from Hasura, to improve performance and/or data resource.What environment is the bug/issue detected in.
What browsers are you seeing the problem on?
What device/platform can the problem be seen?
Steps To Reproduce
Simply navigate to any
fixture
with acompetition
and inspect withDevTools
in< v890
. You'll see data for allcompetitions
being registered.Console Logs (if any)
No response
Anything else?
dev
.The text was updated successfully, but these errors were encountered: