Skip to content

perf(docs): implement high-performance DOM-based scroll spy and progressbar - #42

Merged
Yash-pluto merged 1 commit into
mainfrom
feat/docs
Aug 10, 2026
Merged

Yash-pluto merged 1 commit into
mainfrom
feat/docs

Conversation

@Yash-pluto

Copy link
Copy Markdown
Owner

No description provided.

@Yash-pluto Yash-pluto self-assigned this Aug 10, 2026
@vercel

vercel Bot commented Aug 10, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
refme Ready Ready Preview Aug 10, 2026 7:28am

@coderabbitai

coderabbitai Bot commented Aug 10, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@Yash-pluto, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 29 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: e26f1725-0eea-4cbd-8d11-7d435e87de65

📥 Commits

Reviewing files that changed from the base of the PR and between 7cbc588 and 4e799a4.

📒 Files selected for processing (1)
  • frontend/app/[topic]/TopicLayout.tsx

Comment @coderabbitai help to get the list of available commands.

@Yash-pluto Yash-pluto left a comment

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

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

fixed issue with scroll

@Yash-pluto Yash-pluto added the checked The provided code works. label Aug 10, 2026
@Yash-pluto
Yash-pluto merged commit 35362ed into main Aug 10, 2026
4 checks passed

@anuragg-pixel anuragg-pixel left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Looks good to me

@nausheenfirdous nausheenfirdous left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Lgtm

@Nikhil-phoenix Nikhil-phoenix left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@Yash-pluto , lgtm

@Shraddha-Rawat Shraddha-Rawat left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

I've seen

@Yash-pluto
Yash-pluto deleted the feat/docs branch August 21, 2026 10:27

This branch was successfully deployed

1 active deployment
Preview — 4e799a4a Deployed Aug 10, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

checked The provided code works.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants