Skip to content

fix: Add default debounce & staleTime to file/folder prefetching #346

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

Merged
merged 2 commits into from
Jun 11, 2025

Conversation

brendan-kellam
Copy link
Contributor

@brendan-kellam brendan-kellam commented Jun 11, 2025

We noticed that if you move your cursor across many files in the file tree and then click on one of the files, occasionally the file would never load. This was especially apparent in deployed environments like the demo instance.

My theory is that we were doing too many prefetches too quickly, resulting in some issue when loading the file after the user clicked on it. This PR adds:

  1. A default staleTime (docs) of 5 minutes, meaning that if a user hovers over a file that has already been fetched, it won't be fetched again (until 5 minutes has elapsed).
  2. A default debounceDelay time of 200ms, meaning we will only prefetch when the user's cursor has "settled" on a file.

Summary by CodeRabbit

  • New Features

    • Added support for customizing debounce delay and cache freshness when prefetching file sources and folder contents.
  • Refactor

    • Improved prefetching behavior for file sources and folder contents with configurable options for enhanced performance and flexibility.
  • Bug Fixes

    • Fixed an issue where files occasionally failed to load after rapidly moving the cursor over the file browser.

@brendan-kellam brendan-kellam requested a review from msukkari June 11, 2025 18:32
Copy link

coderabbitai bot commented Jun 11, 2025

Walkthrough

The hooks usePrefetchFileSource and usePrefetchFolderContents were refactored to accept an optional configuration object for debounceDelay and staleTime, with default values set. Both hooks now use a debounced callback for prefetching and apply the specified staleTime to cache freshness in prefetchQuery.

Changes

File(s) Change Summary
packages/web/src/hooks/usePrefetchFileSource.ts Refactored hook to accept config object with debounceDelay and staleTime; uses debounced callback; updated export signature.
packages/web/src/hooks/usePrefetchFolderContents.ts Refactored hook to accept config object with debounceDelay and staleTime; uses debounced callback; updated export signature.
CHANGELOG.md Added a fix note for file loading issues caused by rapid cursor movement in file browser.

Suggested reviewers

  • msukkari

Poem

In the warren’s codey nook,
Two hooks got a fresher look!
Debounced and timed, they leap ahead,
Prefetching files and folders, well-fed.
With options to tweak, and cache set to last,
These rabbits’ queries are lightning fast!
🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9729170 and 29352cf.

📒 Files selected for processing (3)
  • CHANGELOG.md (1 hunks)
  • packages/web/src/hooks/usePrefetchFileSource.ts (1 hunks)
  • packages/web/src/hooks/usePrefetchFolderContents.ts (2 hunks)
🚧 Files skipped from review as they are similar to previous changes (3)
  • CHANGELOG.md
  • packages/web/src/hooks/usePrefetchFileSource.ts
  • packages/web/src/hooks/usePrefetchFolderContents.ts
⏰ Context from checks skipped due to timeout of 90000ms (1)
  • GitHub Check: build
✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🔭 Outside diff range comments (1)
packages/web/src/hooks/usePrefetchFolderContents.ts (1)

21-33: 🛠️ Refactor suggestion

Same dependency oversight as in file-source hook

useDebounceCallback is missing its dependency array, causing a new debounced instance every render.

Apply the same pattern as suggested for usePrefetchFileSource:

-const prefetchFolderContents = useDebounceCallback((repoName: string, revisionName: string, path: string) => {
+const prefetchFolderContents = useDebounceCallback(
+  (repoName: string, revisionName: string, path: string) => {
     queryClient.prefetchQuery({
       queryKey: ['tree', repoName, revisionName, path, domain],
       queryFn: () => unwrapServiceError(
         getFolderContents({ repoName, revisionName, path }, domain)
       ),
       staleTime,
     });
-}, debounceDelay);
+  },
+  debounceDelay,
+  [queryClient, domain, staleTime]
+);
🧹 Nitpick comments (2)
packages/web/src/hooks/usePrefetchFileSource.ts (1)

14-17: Duplicate default values scattered across hooks

Both file & folder hooks hard-code 200 and 5 * 60 * 1000.
Extracting them into a shared constant (e.g. PREFETCH_DEFAULTS) avoids drift and conveys intent.

Nit but worth considering.

packages/web/src/hooks/usePrefetchFolderContents.ts (1)

14-17: Consolidate duplicated configuration constants

Same comment as in the file-source hook: consider centralising debounceDelay and staleTime defaults to avoid magic numbers in multiple files.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 65d6e92 and abcd2b7.

📒 Files selected for processing (2)
  • packages/web/src/hooks/usePrefetchFileSource.ts (1 hunks)
  • packages/web/src/hooks/usePrefetchFolderContents.ts (2 hunks)
🧰 Additional context used
🧬 Code Graph Analysis (1)
packages/web/src/hooks/usePrefetchFileSource.ts (1)
packages/web/src/lib/utils.ts (1)
  • unwrapServiceError (392-399)
⏰ Context from checks skipped due to timeout of 90000ms (3)
  • GitHub Check: build
  • GitHub Check: build
  • GitHub Check: build

@brendan-kellam brendan-kellam force-pushed the bkellam/prefetch_debounce branch from 9729170 to 29352cf Compare June 11, 2025 18:58
@brendan-kellam brendan-kellam merged commit 5ebd07f into main Jun 11, 2025
5 checks passed
@brendan-kellam brendan-kellam deleted the bkellam/prefetch_debounce branch June 11, 2025 20:51
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

Successfully merging this pull request may close these issues.

2 participants