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
Describe the bug
There are many repeated calls to get Issues from GitHub, as seen in the screenshot. This made sense for CATcher, as it was an application which required real-time data. However, WATcher does not need to refresh the issues every 5 seconds, and users can afford to just view non-updated data.
This makes sense as we want to reduce the number of calls.
To Reproduce
Login to WATcher and open network. Issues are polled every 5 seconds using IssueService::startPollIssues.
Desktop (please complete the following information):
OS: MacOS Monterey
Browser Chrome
The text was updated successfully, but these errors were encountered:
This could be a possible solution, but by the nature of WATcher, it might be better to replace the polling with a manual refresh. (perhaps the a sync button).
Describe the bug
There are many repeated calls to get Issues from GitHub, as seen in the screenshot. This made sense for CATcher, as it was an application which required real-time data. However, WATcher does not need to refresh the issues every 5 seconds, and users can afford to just view non-updated data.
This makes sense as we want to reduce the number of calls.
To Reproduce
Login to WATcher and open network. Issues are polled every 5 seconds using
IssueService::startPollIssues
.Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: