Skip to content

feat: [performance improvement] Replace Object.entries().find() with direct O(1) property access#272

Open
anyulled wants to merge 2 commits into
mainfrom
bolt-perf-object-entries-find-3221419730122370004
Open

feat: [performance improvement] Replace Object.entries().find() with direct O(1) property access#272
anyulled wants to merge 2 commits into
mainfrom
bolt-perf-object-entries-find-3221419730122370004

Conversation

@anyulled

Copy link
Copy Markdown
Owner

💡 What: Replaced two instances of Object.entries(obj).find(([k]) => k === key)?.[1] with direct obj[key] access in lib/shared/navigation.ts.
🎯 Why: Object.entries creates an array of tuples in memory and .find performs an O(N) linear search. Direct property access is O(1) and eliminates the intermediate memory allocations, which is especially beneficial in frequently-called functions like getEditionNavigation.
📊 Impact: Reduces garbage collection overhead and drops the time complexity of these lookups from O(N) to O(1).
🔬 Measurement: Verify tests pass via npm run test and check that the site navigation functions exactly as it did before. Build performance (which statically generates many pages using this function) is marginally improved.


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

Refactored `getEditionNavigation` in `lib/shared/navigation.ts` to use
direct object lookups (`cfpData[year]` and `conditions[link.condition]`)
instead of creating intermediate arrays via `Object.entries()` and performing
a linear search via `.find()`.

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 14, 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 14, 2026 8:40am

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 14, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

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 53 minutes and 45 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.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

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: d144221f-42ee-4516-8e1f-a17d75c8bdea

📥 Commits

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

📒 Files selected for processing (2)
  • .jules/bolt.md
  • lib/shared/navigation.ts
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch bolt-perf-object-entries-find-3221419730122370004

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 optimizes code by replacing inefficient Object.entries().find() lookups with direct property access in lib/shared/navigation.ts and updates the documentation in .jules/bolt.md to reflect this best practice. The reviewer provided suggestions to further simplify the property access by removing redundant type assertions and unnecessary ternary checks.

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

Since cfpData is typed as Record<string, CfpTrack[]> and year is a string, you can access the property directly as cfpData[year] without the redundant type assertion as keyof typeof cfpData.

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 = link.condition ? conditions[link.condition as keyof typeof conditions] : true;

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 ternary check link.condition ? ... : true is redundant here because line 41 already guards against a missing link.condition (if (!link.condition) return true;). Additionally, since conditions is typed as Record<NavCondition, boolean> and link.condition is of type NavCondition, the type assertion as keyof typeof conditions is unnecessary. You can simplify this to a direct property access.

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

Refactored `getEditionNavigation` in `lib/shared/navigation.ts` to use
direct object lookups (`cfpData[year]` and `conditions[link.condition]`)
instead of creating intermediate arrays via `Object.entries()` and performing
a linear search via `.find()`. Also fixed formatting in `.jules/bolt.md`.

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