Skip to content
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

Avoid Multiple API Calls for Identical Progress Bar Updates #1297

Open
6 of 10 tasks
shobhan-sundar-goutam opened this issue Dec 18, 2024 · 0 comments
Open
6 of 10 tasks

Comments

@shobhan-sundar-goutam
Copy link

shobhan-sundar-goutam commented Dec 18, 2024

Issue Description

The progress bar update API is currently being invoked multiple times when a user repeatedly clicks the button for the same progress value. This results in redundant API calls and potential performance issues.

Expected Behavior

The API should only be triggered once, even if the button is clicked multiple times for the same progress value.

Current Behavior

When the button is clicked multiple times for the same progress value, the API is triggered repeatedly, causing unnecessary duplicate requests.

Possible Solutions

  1. Abort any ongoing API request before initiating a new one. This ensures only the latest request is processed.
  2. Make the UPDATE button clickable only when the progress value has changed. After clicking the button, either disable it or display a loader to prevent multiple API calls until the current request is completed.

Screenshots

progress-update-issue.mp4

Reproducibility

  • This issue is reproducible
  • This issue is not reproducible

Steps to Reproduce

  1. Click on UPDATE button for updating progress bar on the Update Progress modal of Tasks
  2. Click multiple times while changing the value.

Severity/Priority

  • Critical
  • High
  • Medium
  • Low

Checklist

  • I have read and followed the project's code of conduct.
  • I have searched for similar issues before creating this one.
  • I have provided all the necessary information to understand and reproduce the issue.
  • I am willing to contribute to the resolution of this issue.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant