Skip to content

feat: [performance improvement]#285

Open
anyulled wants to merge 1 commit into
mainfrom
bolt-perf-object-lookup-6628073051213857732
Open

feat: [performance improvement]#285
anyulled wants to merge 1 commit into
mainfrom
bolt-perf-object-lookup-6628073051213857732

Conversation

@anyulled

Copy link
Copy Markdown
Owner

💡 What: Replaced Object.entries(obj).find(([key]) => key === target)?.[1] with direct O(1) property access obj[target as keyof typeof obj] in lib/shared/navigation.ts for both cfpData and conditions.

🎯 Why: To eliminate unnecessary array allocations (Object.entries creates a new array of arrays) and avoid linear O(N) search times during layout and navigation rendering, which happens frequently.

📊 Impact: Reduces amortized O(N) operations to strictly O(1), lowering GC overhead and slightly improving server-side render times for navigation links across all pages.

🔬 Measurement: The Next.js build completed quickly, and npm run test and npm run lint pass successfully without regressions. The code continues to handle missing keys gracefully by returning undefined.


PR created automatically by Jules for task 6628073051213857732 started by @anyulled

…ct lookup in navigation.ts

Replaces O(N) `Object.entries(obj).find` iterations with O(1) direct property access
(`obj[key]`) in `lib/shared/navigation.ts` to reduce memory allocations and
improve layout execution speed.

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
@google-labs-jules

Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

@vercel

vercel Bot commented Jun 20, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
devbcn-nextjs Error Error Jun 20, 2026 8:20am

Request Review

@qodo-code-review

Copy link
Copy Markdown

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

@coderabbitai

coderabbitai Bot commented Jun 20, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

@anyulled, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 54 minutes and 25 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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 credits.

🚦 How do rate limits work?

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

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, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 0f8d8cac-69ce-4ab7-a94a-bbfe3b660fe2

📥 Commits

Reviewing files that changed from the base of the PR and between b2e2a82 and 3c92bb7.

📒 Files selected for processing (1)
  • lib/shared/navigation.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch bolt-perf-object-lookup-6628073051213857732

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

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

@gemini-code-assist gemini-code-assist Bot 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.

Code Review

This pull request simplifies property lookups in lib/shared/navigation.ts by replacing complex Object.entries().find() lookups with direct property access. The feedback points out that the type assertions used during these lookups are redundant and suggests cleaner, direct property access without casting.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment thread lib/shared/navigation.ts
const hasSchedule = schedule.length > 0;

const editionCfp = Object.entries(cfpData).find(([y]) => y === year)?.[1];
const editionCfp = cfpData[year as keyof typeof cfpData];

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.

medium

The type assertion as keyof typeof cfpData is redundant. Since cfpData is defined as Record<string, CfpTrack[]> and year is of type string, you can perform direct property access without any type casting.

Suggested change
const editionCfp = cfpData[year as keyof typeof cfpData];
const editionCfp = cfpData[year];

Comment thread lib/shared/navigation.ts
.filter((link) => {
if (!link.condition) return true;
const conditionValue = Object.entries(conditions).find(([key]) => key === link.condition)?.[1];
const conditionValue = conditions[link.condition as keyof typeof conditions];

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.

medium

The type assertion as keyof typeof conditions is redundant. Since conditions is typed as Record<NavCondition, boolean> and link.condition is of type NavCondition (guaranteed by the non-nullability check on line 41), you can access the property directly without casting.

Suggested change
const conditionValue = conditions[link.condition as keyof typeof conditions];
const conditionValue = conditions[link.condition];

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant