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
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 /api/jira/get-projects and /api/github/get-installed-repos endpoints are being called multiple times unnecessarily. This results in redundant network requests, which significantly slows down the performance of the /settings/integrations/jira page.
How to reproduce
Navigate to the /settings/integrations/jira page.
Open the browser's network console.
Observe that the /api/jira/get-projects endpoint is called twice in quick succession.
Similarly, notice that the /api/github/get-installed-repos endpoint is invoked twice simultaneously.
How to fix
Identify Redundant Calls: Review the components and hooks responsible for fetching data on the /settings/integrations/jira page to identify where the duplicate API calls are initiated.
Optimize Data Fetching Logic:
Ensure that data-fetching functions are not called multiple times due to re-renders or improper dependency arrays in hooks like useEffect.
Consolidate API calls where possible to prevent simultaneous requests.
Implement Caching: Utilize caching strategies to store and reuse fetched data, reducing the need for repeated API requests.
Debounce or Throttle Requests: If applicable, implement debounce or throttle mechanisms to limit the frequency of API calls triggered by user interactions.
Refactor Code: Update the relevant components and utilities in the app, components, or utils directories to incorporate the above optimizations.
By addressing the redundant API calls and optimizing the data fetching strategy, the performance of the /settings/integrations/jira page will be significantly improved.
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.
![gitauto-for-dev[bot]](https://avatars.githubusercontent.com/in/828792?s=60&v=4){kind=small}
Resolves #133
Why the bug occurs
The
/api/jira/get-projectsand/api/github/get-installed-reposendpoints are being called multiple times unnecessarily. This results in redundant network requests, which significantly slows down the performance of the/settings/integrations/jirapage.How to reproduce
/settings/integrations/jirapage./api/jira/get-projectsendpoint is called twice in quick succession./api/github/get-installed-reposendpoint is invoked twice simultaneously.How to fix
/settings/integrations/jirapage to identify where the duplicate API calls are initiated.useEffect.app,components, orutilsdirectories to incorporate the above optimizations.By addressing the redundant API calls and optimizing the data fetching strategy, the performance of the
/settings/integrations/jirapage will be significantly improved.Test these changes locally