feat: [performance improvement]

[anyulled]

💡 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.
🎯 Why: Iterating over an array of object entries to find a matching key is an O(N) operation that generates unnecessary garbage collection overhead by creating an array of tuples.
📊 Impact: Eliminates O(N) array allocation (Object.entries()) and linear search overhead. Direct property access achieves the exact same result in O(1) time and is much more efficient.
🔬 Measurement: Verified the code structure using npm run lint and tests using npm run test -- __tests__/lib/shared/navigation.test.ts.

---

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

Summary by CodeRabbit

• Documentation
  • Added a new learning note covering a React performance optimization pattern.
• Bug Fixes
  • Improved navigation-related lookups to use direct access instead of searching through lists, reducing unnecessary work.
  • Streamlined link filtering logic for better efficiency and responsiveness.

[google-labs-jules]

👋 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]

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

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

[qodo-code-review]

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]

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 26 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 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 see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 079aa647-e01a-4ff2-95d8-974128896336

📥 Commits

Reviewing files that changed from the base of the PR and between 41095dd and b0cd8df.

📒 Files selected for processing (1)

• .jules/bolt.md

📝 Walkthrough

Walkthrough

Two Object.entries(obj).find(...) calls in lib/shared/navigation.ts are replaced with direct O(1) key indexing using TypeScript's keyof typeof cast. A new entry in .jules/bolt.md records this pattern as a project learning note.

Changes

O(1) Property Lookup in Navigation

Layer / File(s)	Summary
Direct key indexing in navigation helpers and journal note lib/shared/navigation.ts, .jules/bolt.md	editionCfp now uses cfpData[year as keyof typeof cfpData] and conditionValue uses conditions[link.condition as keyof typeof conditions], replacing two Object.entries().find() calls. A new bolt.md entry documents the pattern.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐇 No more searching through arrays so wide,
A key is all needed — just look inside!
cfpData[year] in a blink,
No entries to scan, no chains to link.
Hop straight to the value, swift and free,
O(1) forever — that's the life for me! 🥕

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.
Title check	❓ Inconclusive	The title is generic and does not describe the specific navigation lookup optimization in this PR.	Use a descriptive title such as "Optimize navigation lookups with direct property access".

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch bolt/o1-object-access-1431790661249455027

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[gemini-code-assist]

Code Review

This pull request optimizes property lookups in lib/shared/navigation.ts by replacing O(N) Object.entries().find() operations with O(1) direct property access, and documents this optimization in .jules/bolt.md. The reviewer points out a redundant type assertion as keyof typeof conditions when accessing conditions[link.condition], as the types are already compatible and type-safe.

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.

[gemini-code-assist]

Since conditions is explicitly typed as Record<NavCondition, boolean> and link.condition is guaranteed to be of type NavCondition after the truthiness check, the type assertion as keyof typeof conditions is redundant. You can access the property directly using conditions[link.condition], which is cleaner and fully type-safe.

Suggested change

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