Optimizing API calls and adding cache #94

vedansh-5 · 2025-05-28T17:41:35Z

Description

Optimized GitHub data fetching by implementing persistent caching, debouncing bursts of API calls, and enabling parallel API requests. These improvements significantly reduce redundant network traffic and enhance performance. The codebase has also been modernized with native fetch, async/await, and cleaner variable declarations, along with minor UI enhancements.
Fixes #104
Key Features

Persistent Caching: Added a client-side cache layer with TTL and state restoration to avoid redundant API calls.

Debouncing & Queuing: Prevents API spamming by intelligently delaying burst requests.

Parallel Fetching: Fetches issues, PR reviews, and user data concurrently to reduce wait times.

Enhancements

Migrated from jQuery AJAX to native fetch using Promise.all and async/await.

Refactored variable declarations using let and const for cleaner, safer code.

Introduced debug logging for cache and network operations.

Summary by Sourcery

Optimize GitHub data fetching by adding a persistent cache layer, debouncing burst requests, and parallelizing API calls, while modernizing code with fetch, async/await, and variable declaration refactoring plus UI toggle styling enhancements.

New Features:

Introduce persistent client-side caching for GitHub API data with TTL and storage restoration
Implement request debouncing, queuing, and parallel fetching of GitHub issues, PR reviews, and user data

Enhancements:

Migrate from jQuery AJAX to native fetch with Promise.all and modern async/await patterns
Refactor codebase to use let/const declarations and add debug logging for cache and fetch operations
Add CSS classes for selected/unselected toggle labels with smooth transition effects

sourcery-ai · 2025-05-28T17:41:40Z

Reviewer's Guide

This PR enhances performance of GitHub data fetching by introducing a client-side cache with persistence and TTL, debouncing and queuing of API calls to prevent bursts, and parallelizing data fetches; it also modernizes the codebase with native fetch, ES6 syntax, debug logging, and UI styling improvements.

Class Diagram of the New Caching System in `scrumHelper.js`

classDiagram
    class githubCache {
      <<JavaScript Object>>
      +data: object
      +cacheKey: string
      +timestamp: number
      +ttl: number
      +fetching: boolean
      +queue: object[]
      +errors: object
      +errorTTL: number
      +MAX_CACHE_SIZE: number
    }

    class CacheController {
      <<Conceptual Grouping of Functions>>
      #githubCache: githubCache
      +fetchGithubData(): Promise~void~
      +saveToStorage(dataToSave: object): Promise~boolean~
      +loadFromStorage(): Promise~boolean~
      +updateCache(dataToUpdate: object): void
      +processGithubData(dataToProcess: object): void
      +verifyCacheStatus(): void
      +getChromeData(): void
      +log(...args): void
      +logError(...args): void
    }

    CacheController ..> githubCache : manages and uses
    CacheController ..> chrome.storage.local : interacts via save/load

File-Level Changes

Change	Details	Files
Introduce a persistent TTL cache for GitHub data	Added global githubCache object with data, cacheKey, timestamp, ttl, queue, and error tracking Implemented saveToStorage and loadFromStorage functions using chrome.storage.local Invalidate cache on key mismatch and update timestamp on cache writes	`src/scripts/scrumHelper.js`
Debounce and queue concurrent API requests	Throttle requests with a 500ms delay before fetching Use fetching flag and queue array to buffer overlapping calls Resolve or reject queued promises once fetch completes	`src/scripts/scrumHelper.js`
Parallelize data fetching with async/await and Promise.all	Construct issue, PR, and user URLs dynamically with template strings Fetch issues, PR reviews, and user data concurrently Process and cache all three responses together	`src/scripts/scrumHelper.js`
Migrate from jQuery AJAX to native fetch and modernize syntax	Replaced $.ajax calls with fetch and async/await Converted var declarations to let/const and used template literals Refactored callback flows into async functions	`src/scripts/scrumHelper.js` `src/scripts/main.js`
Add configurable debug logging and error handling	Introduced DEBUG flag with log and logError wrappers Log key cache events, fetch status, and storage operations Catch fetch errors and propagate to queued requests	`src/scripts/scrumHelper.js`
Enhance UI toggle styling and configuration behavior	Added .selectedLabel and .unselectedLabel CSS classes with transitions Update main.js to toggle label classes on configuration elements Sync toggle state changes to chrome.storage.local	`src/index.css` `src/scripts/main.js`

Tips and commands

Interacting with Sourcery

Trigger a new review: Comment @sourcery-ai review on the pull request.
Continue discussions: Reply directly to Sourcery's review comments.
Generate a GitHub issue from a review comment: Ask Sourcery to create an
issue from a review comment by replying to it. You can also reply to a
review comment with @sourcery-ai issue to create an issue from it.
Generate a pull request title: Write @sourcery-ai anywhere in the pull
request title to generate a title at any time. You can also comment
@sourcery-ai title on the pull request to (re-)generate the title at any time.
Generate a pull request summary: Write @sourcery-ai summary anywhere in
the pull request body to generate a PR summary at any time exactly where you
want it. You can also comment @sourcery-ai summary on the pull request to
(re-)generate the summary at any time.
Generate reviewer's guide: Comment @sourcery-ai guide on the pull
request to (re-)generate the reviewer's guide at any time.
Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
pull request to resolve all Sourcery comments. Useful if you've already
addressed all the comments and don't want to see them anymore.
Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
request to dismiss all existing Sourcery reviews. Especially useful if you
want to start fresh with a new review - don't forget to comment
@sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

Enable or disable review features such as the Sourcery-generated pull request
summary, the reviewer's guide, and others.
Change the review language.
Add, remove or edit custom review instructions.
Adjust other review settings.

Getting Help

Contact our support team for questions or feedback.
Visit our documentation for detailed guides and information.
Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

sourcery-ai

Hey @vedansh-5 - I've reviewed your changes and found some issues that need to be addressed.

Blocking issues:

Incorrect storage API method and undefined variable (link)

General comments:

Replace the call to chrome.storage.local.setAttribute with chrome.storage.local.set, since setAttribute is not a valid API and will prevent your cache from persisting.
Remove the duplicated declaration of let refreshButton_Placed inside allIncluded which shadows the global variable and may lead to unexpected behavior.
Make the DEBUG flag configurable (e.g. via environment or options) so you can disable verbose logging in production and avoid performance overhead.

Here's what I looked at during the review

🔴 General issues: 1 blocking issue, 5 other issues
🟢 Security: all looks good
🟢 Testing: all looks good
🟢 Documentation: all looks good

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

src/scripts/scrumHelper.js

vedansh-5 · 2025-05-29T12:55:17Z

caching.mp4

I have successfully added the feature of caching of data in between API calls, as can be seen in the video, API calls are not being made to GitHub API and the data stored in cache is being used. This PR is not ready to be merged yet, I still have to add a component in UI using which we can manually trigger fetching of the data, TTL is set to 10 minutes.
@Preeti9764 : Could you take a look whenever you have some time.

vedansh-5 · 2025-05-29T12:57:20Z

@sourcery-ai review

sourcery-ai

Hey @vedansh-5 - I've reviewed your changes - here's some feedback:

Extract the duplicated date‐formatting logic and cache/fetch utilities into shared modules to DRY up both main.js and scrumHelper.js.
Clean up leftover commented-out code and debug scaffolding (e.g. remove console.log blocks and fix the console.wanr typo) before merging.
Consider moving the GitHub cache/debounce/queue logic into its own service layer to simplify error handling and make the core script more maintainable.

Here's what I looked at during the review

🟢 General issues: all looks good
🟢 Security: all looks good
🟢 Testing: all looks good
🟢 Documentation: all looks good

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

sourcery-ai · 2025-05-29T13:04:17Z

src/scripts/main.js

 	chrome.storage.local.set({ enableToggle: value });
 }
 function handleStartingDateChange() {
-	var value = startingDateElement.value;
+	let value = startingDateElement.value;


suggestion (code-quality): Prefer object destructuring when accessing and using properties. (use-object-destructuring)

Suggested change

let value = startingDateElement.value;

let {value} = startingDateElement;

Explanation
Object destructuring can often remove an unnecessary temporary reference, as well as making your code more succinct.

From the Airbnb Javascript Style Guide

sourcery-ai · 2025-05-29T13:04:18Z

src/scripts/main.js

 	chrome.storage.local.set({ startingDate: value });
 }
 function handleEndingDateChange() {
-	var value = endingDateElement.value;
+	let value = endingDateElement.value;


suggestion (code-quality): Prefer object destructuring when accessing and using properties. (use-object-destructuring)

Suggested change

let value = endingDateElement.value;

let {value} = endingDateElement;

Explanation
Object destructuring can often remove an unnecessary temporary reference, as well as making your code more succinct.

From the Airbnb Javascript Style Guide

sourcery-ai · 2025-05-29T13:04:18Z

src/scripts/main.js

@@ -136,20 +142,30 @@ function getToday() {
 }

 function handleGithubUsernameChange() {
-	var value = githubUsernameElement.value;
+	let value = githubUsernameElement.value;


suggestion (code-quality): Prefer object destructuring when accessing and using properties. (use-object-destructuring)

Suggested change

let value = githubUsernameElement.value;

let {value} = githubUsernameElement;

Explanation
Object destructuring can often remove an unnecessary temporary reference, as well as making your code more succinct.

From the Airbnb Javascript Style Guide

sourcery-ai · 2025-05-29T13:04:18Z

src/scripts/main.js

 	chrome.storage.local.set({ githubUsername: value });
 }
 function handleProjectNameChange() {
-	var value = projectNameElement.value;
+	let value = projectNameElement.value;


suggestion (code-quality): Prefer object destructuring when accessing and using properties. (use-object-destructuring)

Suggested change

let value = projectNameElement.value;

let {value} = projectNameElement;

Explanation
Object destructuring can often remove an unnecessary temporary reference, as well as making your code more succinct.

From the Airbnb Javascript Style Guide

sourcery-ai · 2025-05-29T13:04:18Z

src/scripts/main.js

 function handleUserReasonChange() {
-	var value = userReasonElement.value;
+	let value = userReasonElement.value;


suggestion (code-quality): Prefer object destructuring when accessing and using properties. (use-object-destructuring)

Suggested change

let value = userReasonElement.value;

let {value} = userReasonElement;

Explanation
Object destructuring can often remove an unnecessary temporary reference, as well as making your code more succinct.

From the Airbnb Javascript Style Guide

sourcery-ai · 2025-05-29T13:04:19Z

src/scripts/scrumHelper.js

-			var title = item.title;
-			var number = item.number;
-			var li = '';
+		let items = githubIssuesData.items;


suggestion (code-quality): Prefer object destructuring when accessing and using properties. (use-object-destructuring)

Suggested change

let items = githubIssuesData.items;

let {items} = githubIssuesData;

Explanation
Object destructuring can often remove an unnecessary temporary reference, as well as making your code more succinct.

From the Airbnb Javascript Style Guide

sourcery-ai · 2025-05-29T13:04:19Z

src/scripts/scrumHelper.js

+		}
+		for (let i = 0; i < items.length; i++) {
+			let item = items[i];
+			let html_url = item.html_url;


suggestion (code-quality): Prefer object destructuring when accessing and using properties. (use-object-destructuring)

Suggested change

let html_url = item.html_url;

let {html_url} = item;

Explanation
Object destructuring can often remove an unnecessary temporary reference, as well as making your code more succinct.

From the Airbnb Javascript Style Guide

sourcery-ai · 2025-05-29T13:04:19Z

src/scripts/scrumHelper.js

+		for (let i = 0; i < items.length; i++) {
+			let item = items[i];
+			let html_url = item.html_url;
+			let repository_url = item.repository_url;


suggestion (code-quality): Prefer object destructuring when accessing and using properties. (use-object-destructuring)

Suggested change

let repository_url = item.repository_url;

let {repository_url} = item;

Explanation
Object destructuring can often remove an unnecessary temporary reference, as well as making your code more succinct.

From the Airbnb Javascript Style Guide

sourcery-ai · 2025-05-29T13:04:19Z

src/scripts/scrumHelper.js

+			let html_url = item.html_url;
+			let repository_url = item.repository_url;
+			let project = repository_url.substr(repository_url.lastIndexOf('/') + 1);
+			let title = item.title;


suggestion (code-quality): Prefer object destructuring when accessing and using properties. (use-object-destructuring)

Suggested change

let title = item.title;

let {title} = item;

Explanation
Object destructuring can often remove an unnecessary temporary reference, as well as making your code more succinct.

From the Airbnb Javascript Style Guide

sourcery-ai · 2025-05-29T13:04:19Z

src/scripts/scrumHelper.js

+			let repository_url = item.repository_url;
+			let project = repository_url.substr(repository_url.lastIndexOf('/') + 1);
+			let title = item.title;
+			let number = item.number;


suggestion (code-quality): Prefer object destructuring when accessing and using properties. (use-object-destructuring)

Suggested change

let number = item.number;

let {number} = item;

Explanation
Object destructuring can often remove an unnecessary temporary reference, as well as making your code more succinct.

From the Airbnb Javascript Style Guide

hpdang · 2025-05-30T09:48:26Z

when testing this PR locally, I get the following error in the console:

popup.html:1 Error handling response: ReferenceError: labelElement is not defined
at handleLastWeekContributionChange (chrome-extension://habmeegbbkhocamkcglcopcdehmenaah/scripts/main.js:107:4)
at handleGsocClick (chrome-extension://habmeegbbkhocamkcglcopcdehmenaah/scripts/main.js:185:2)
at chrome-extension://habmeegbbkhocamkcglcopcdehmenaah/scripts/main.js:65:5
main.js:107 Uncaught ReferenceError: labelElement is not defined
at handleLastWeekContributionChange (main.js:107:4)
at HTMLAnchorElement.handleGsocClick (main.js:185:2)

vedansh-5 · 2025-05-30T10:00:46Z

when testing this PR locally, I get the following error in the console:

popup.html:1 Error handling response: ReferenceError: labelElement is not defined at handleLastWeekContributionChange (chrome-extension://habmeegbbkhocamkcglcopcdehmenaah/scripts/main.js:107:4) at handleGsocClick (chrome-extension://habmeegbbkhocamkcglcopcdehmenaah/scripts/main.js:185:2) at chrome-extension://habmeegbbkhocamkcglcopcdehmenaah/scripts/main.js:65:5 main.js:107 Uncaught ReferenceError: labelElement is not defined at handleLastWeekContributionChange (main.js:107:4) at HTMLAnchorElement.handleGsocClick (main.js:185:2)

Thanks for pointing this out, this is a rebase discrepancy, I've fixed the labelElement definition, will commit along with other enhancements in the pr.

vedansh-5 · 2025-05-30T17:00:13Z

@hpdang @mariobehling Please take a look whenever you have some time, with the latest changes optimization of API requests and content caching along with API debouncing is successfully implemented.
I could use another pair of eyes to skim through the code @Preeti9764
Thanks!

Preeti9764

Could you please confirm if the 'Refresh Data (bypass cache)' button is successfully clearing the cached GitHub data and triggering fresh API calls? Also, is the cache properly repopulated after the reload?

vedansh-5 · 2025-05-31T18:55:29Z

Could you please confirm if the 'Refresh Data (bypass cache)' button is successfully clearing the cached GitHub data and triggering fresh API calls? Also, is the cache properly repopulated after the reload?

Yes it clears the data, and populates it after reload.

vedansh-5 · 2025-05-31T18:57:51Z

Could you please confirm if the 'Refresh Data (bypass cache)' button is successfully clearing the cached GitHub data and triggering fresh API calls? Also, is the cache properly repopulated after the reload?

Yes it clears the data, and populates it after reload.

I have checked it extensively. Did you locally try the extension, there's a DEBUG variable in ScrumHelper.js which is now set to false, you can set it to true to get a clearer picture.
Thanks!

vedansh-5 · 2025-05-31T19:30:25Z

@Preeti9764 Does the PR looks good to merge?

Preeti9764 · 2025-06-01T07:18:54Z

I have checked it extensively. Did you locally try the extension, there's a DEBUG variable in ScrumHelper.js which is now set to false, you can set it to true to get a clearer picture. Thanks!

Yes , i locally tested it but i could not find the reviewed pr in scrum generated. can you please check this once. Other things are working fine as far i have checked.

vedansh-5 · 2025-06-01T07:22:07Z

I have checked it extensively. Did you locally try the extension, there's a DEBUG variable in ScrumHelper.js which is now set to false, you can set it to true to get a clearer picture. Thanks!

Yes , i locally tested it but i could not find the reviewed pr in scrum generated. can you please check this once. Other things are working fine as far i have checked.

I generated this rn.

Preeti9764 · 2025-06-01T16:16:12Z

After making changes of this pr the reviewed prs are not visible in the left one .
@vedansh-5 Please look this once.

vedansh-5 · 2025-06-01T16:19:58Z

After making changes of this pr the reviewed prs are not visible in the left one . @vedansh-5 Please look this once.

Thanks for pointing this out, I'll look for the cause and fix it.

vedansh-5 · 2025-06-05T10:59:43Z

@Preeti9764 I made changes in the code and its now injecting the reviewed PRs, can you check if its working for you or not.
Once you confirm I'll move onto resolving the conflicts.
Thanks!

Preeti9764 · 2025-06-06T12:55:36Z

@Preeti9764 I made changes in the code and its now injecting the reviewed PRs, can you check if its working for you or not.

yes, i checked it the issue of reviewed pr is not there any more...but i found the code currently performs repetitive DOM queries without any caching mechanism. Can you look at that .

vedansh-5 · 2025-06-06T13:30:31Z

@Preeti9764 I made changes in the code and its now injecting the reviewed PRs, can you check if its working for you or not.

yes, i checked it the issue of reviewed pr is not there any more...but i found the code currently performs repetitive DOM queries without any caching mechanism. Can you look at that .

Caching is implemented, could you please tell what observations of yours make you say this?

vedansh-5 · 2025-06-06T14:26:18Z

@Preeti9764 I made changes in the code and its now injecting the reviewed PRs, can you check if its working for you or not.

yes, i checked it the issue of reviewed pr is not there any more...but i found the code currently performs repetitive DOM queries without any caching mechanism. Can you look at that .

caching.mp4

As can be seen in this video, fetch requests are made only for the first time and not after that. It would be better if you share your network logs for the same to confirm the issue. Thanks!

Preeti9764 · 2025-06-06T14:37:21Z

@Preeti9764 I made changes in the code and its now injecting the reviewed PRs, can you check if its working for you or not.

yes, i checked it the issue of reviewed pr is not there any more...but i found the code currently performs repetitive DOM queries without any caching mechanism. Can you look at that .

Caching is implemented, could you please tell what observations of yours make you say this?

The Dom queries are repeative, which are not good for performance optimisation .

vedansh-5 · 2025-06-06T14:43:01Z

@Preeti9764 I made changes in the code and its now injecting the reviewed PRs, can you check if its working for you or not.

yes, i checked it the issue of reviewed pr is not there any more...but i found the code currently performs repetitive DOM queries without any caching mechanism. Can you look at that .

Caching is implemented, could you please tell what observations of yours make you say this?

The Dom queries are repeative, which are not good for performance optimisation .

Your previous comment was misleading, stating caching is not implemented. Also could you please share your logs for the repetitive DOM queries, given the behavior of extension, they should be justified :)

Preeti9764 · 2025-06-06T15:07:52Z

Your previous comment was misleading, stating caching is not implemented. Also could you please share your logs for the repetitive DOM queries, given the behavior of extension, they should be justified :)

I apologize if my comment about caching wasn't clear enough. Let me clarify my observation:
Every time getEditorElements() method is called, it:
Searches the entire DOM tree
Creates new element references
I was talking about caching not implemented in this part. Thanks!

vedansh-5 · 2025-06-06T15:13:56Z

Your previous comment was misleading, stating caching is not implemented. Also could you please share your logs for the repetitive DOM queries, given the behavior of extension, they should be justified :)

I apologize if my comment about caching wasn't clear enough. Let me clarify my observation: Every time getEditorElements() method is called, it: Searches the entire DOM tree Creates new element references I was talking about caching not implemented in this part. Thanks!

Appreciate your point, although it has minimal effect on the speed but this might cause memory leaks in some cases. I will push changes for it soon. ☺️

vedansh-5 · 2025-06-10T08:56:52Z

Hello @Preeti9764 after the rebase content is not being injected in popup, Could you please take a look what's wrong? Thanks

vedansh-5 · 2025-06-10T11:44:24Z

@hpdang
I have resolved the errors in this PR and is ready to be merged with all the functionalities intact. However this PR will need changes when the #83 will be merged. As soon as new UI pr is merged I will start working towards resolving the conflicts for this PR to successfully implement caching and bypass cache into the new UI.

Preeti9764 · 2025-06-10T12:40:12Z

Hello @Preeti9764 after the rebase content is not being injected in popup, Could you please take a look what's wrong? Thanks

Hey , I have checked this ,the issue which i found is every line of scrum is coming twice .

this is beacause you may have called a function twice.

Preeti9764 · 2025-06-10T13:04:24Z

I found that- writeGithubIssuesPrs(),writeGithubPrsReviews() are called twice, which causes this issue firstly in the function processGithubData() and in intervals also, which mostly causes this issue. I have made changes in the scrumHelper.js file that resolve this. Have and look for a reference and edit that file. I have sent you personally.

vedansh-5 · 2025-06-10T13:07:31Z

Yes I know the calls which resulted in the error, for me it was behaving weirdly earlier, maybe something with github servers and my IP, i removed the lines and made changes for correct indentation. I'll push it as soon as github loads. Thanks!

…

On Tue, Jun 10, 2025 at 6:34 PM Preeti Yadav ***@***.***> wrote: *Preeti9764* left a comment (fossasia/scrum_helper#94) <#94 (comment)> I found that- writeGithubIssuesPrs(),writeGithubPrsReviews() are called twice, which causes this issue firstly in the function processGithubData() and in intervals also, which mostly causes this issue. I have made changes in the scrumHelper.js file that resolve this. Have and look for reference and edit that file. — Reply to this email directly, view it on GitHub <#94 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ASRZUKWQAVAL45XFKAA767T3C3JW7AVCNFSM6AAAAAB6DO66ROVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDSNJZGE2DGNJYGY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

vedansh-5 · 2025-06-11T09:19:45Z

@hpdang @Preeti9764 I have rebased this PR and made changes in the UI accordingly, please take a look whenever you can.
This pr is now ready to be merged. Thanks!

hpdang · 2025-06-11T15:33:10Z

@vedansh-5 Why do you want to put the Refresh Data (bypass cache) on the UI? What kind of behavior you expect from the user?

vedansh-5 · 2025-06-11T15:37:29Z

@vedansh-5 Why do you want to put the Refresh Data (bypass cache) on the UI? What kind of behavior you expect from the user?

I have added the Refresh Data(bypass cache) button on the UI to support edge cases where users suspect outdated or incorrect data.
TTL is of 10 minutes, if a user fetched the data a few mins ago and then pushed new code or reviewed a PR they can trigger a manual fetch of data.

hpdang · 2025-06-11T15:41:23Z

I am not sure if that is a good idea, it is too dominant while is not a core feature. When I clicked on it, it shows Fail to Refresh. And it will raise unnecessary question to a new user. They will ask themselves, what it is for.

vedansh-5 · 2025-06-11T15:45:36Z

I am not sure if that is a good idea, it is too dominant while is not a core feature. When I clicked on it, it shows Fail to Refresh. And it will raise unnecessary question to a new user. They will ask themselves, what it is for.

I can remove the button and decrease the TTL to 5 mins. How does it sound to you?

vedansh-5 · 2025-06-11T15:51:36Z

I am not sure if that is a good idea, it is too dominant while is not a core feature. When I clicked on it, it shows Fail to Refresh. And it will raise unnecessary question to a new user. They will ask themselves, what it is for.

I can remove the button and decrease the TTL to 5 mins. How does it sound to you?

I see a scoping error, let me fix it, maybe then we can keep it. Thanks.

vedansh-5 · 2025-06-11T16:04:30Z

@hpdang

I have moved the button down, after generate and copy button, users won't see it firsthand and wonder what's in it for them. Also I have added a note below it.
The fail to refresh issue is solved too. Thanks for pointing this out.

vedansh-5 · 2025-06-11T16:11:10Z

I have resolved the conflicts.

vedansh-5 · 2025-06-13T05:16:17Z

@hpdang could you please take a look whenever you have some time? Thanks!

vedansh-5 self-assigned this May 28, 2025

sourcery-ai bot reviewed May 28, 2025

View reviewed changes

vedansh-5 force-pushed the optapi branch from 37234e6 to 6957a33 Compare May 28, 2025 17:48

mariobehling requested a review from hpdang May 28, 2025 18:18

vedansh-5 force-pushed the optapi branch from b5b1117 to 7378449 Compare May 28, 2025 19:34

vedansh-5 requested review from mariobehling and Preeti9764 May 29, 2025 12:51

sourcery-ai bot reviewed May 29, 2025

View reviewed changes

Preeti9764 reviewed May 31, 2025

View reviewed changes

vedansh-5 mentioned this pull request Jun 10, 2025

[Feature] new UI #83

Merged

Preeti9764 mentioned this pull request Jun 11, 2025

To show Commits in Scrum Report #114

Merged

3 tasks

vedansh-5 closed this Jun 16, 2025

vedansh-5 force-pushed the optapi branch from 2381d17 to b2ae50d Compare June 16, 2025 17:01

vedansh-5 deleted the optapi branch June 16, 2025 17:06

	let value = startingDateElement.value;
	let {value} = startingDateElement;

	let value = endingDateElement.value;
	let {value} = endingDateElement;

	let value = githubUsernameElement.value;
	let {value} = githubUsernameElement;

	let value = projectNameElement.value;
	let {value} = projectNameElement;

	let value = userReasonElement.value;
	let {value} = userReasonElement;

	let items = githubIssuesData.items;
	let {items} = githubIssuesData;

	let repository_url = item.repository_url;
	let {repository_url} = item;

Optimizing API calls and adding cache #94

Optimizing API calls and adding cache #94

Uh oh!

Conversation

vedansh-5 commented May 28, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Summary by Sourcery

Uh oh!

sourcery-ai bot commented May 28, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Reviewer's Guide

Class Diagram of the New Caching System in scrumHelper.js

File-Level Changes

Interacting with Sourcery

Customizing Your Experience

Getting Help

Uh oh!

sourcery-ai bot left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

vedansh-5 commented May 29, 2025

Uh oh!

vedansh-5 commented May 29, 2025

Uh oh!

sourcery-ai bot left a comment

Choose a reason for hiding this comment

Uh oh!

sourcery-ai bot May 29, 2025

Choose a reason for hiding this comment

Uh oh!

sourcery-ai bot May 29, 2025

Choose a reason for hiding this comment

Uh oh!

sourcery-ai bot May 29, 2025

Choose a reason for hiding this comment

Uh oh!

sourcery-ai bot May 29, 2025

Choose a reason for hiding this comment

Uh oh!

sourcery-ai bot May 29, 2025

Choose a reason for hiding this comment

Uh oh!

sourcery-ai bot May 29, 2025

Choose a reason for hiding this comment

Uh oh!

sourcery-ai bot May 29, 2025

Choose a reason for hiding this comment

Uh oh!

sourcery-ai bot May 29, 2025

Choose a reason for hiding this comment

Uh oh!

sourcery-ai bot May 29, 2025

Choose a reason for hiding this comment

Uh oh!

sourcery-ai bot May 29, 2025

Choose a reason for hiding this comment

Uh oh!

hpdang commented May 30, 2025

Uh oh!

vedansh-5 commented May 30, 2025

Uh oh!

vedansh-5 commented May 30, 2025

Uh oh!

Preeti9764 left a comment • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

vedansh-5 commented May 31, 2025

Uh oh!

vedansh-5 commented May 28, 2025 •

edited

Loading

sourcery-ai bot commented May 28, 2025 •

edited

Loading

Class Diagram of the New Caching System in `scrumHelper.js`

Preeti9764 left a comment •

edited

Loading

vedansh-5 commented May 31, 2025 •

edited

Loading

vedansh-5 commented Jun 5, 2025 •

edited

Loading

vedansh-5 commented Jun 6, 2025 •

edited

Loading

vedansh-5 commented Jun 6, 2025 •

edited

Loading

Preeti9764 commented Jun 10, 2025 •

edited

Loading

vedansh-5 commented Jun 10, 2025 via email •

edited

Loading

vedansh-5 commented Jun 11, 2025 •

edited

Loading