Key Factors Redesign 2nd iteration

[ncarazon]

This PR implements the 1st iteration of the Key Factors Redesign

Iteration 2: Expanded Overlay

• Clicking a key factor opens an overlay showing the key factor + source comment side-by-side
• Mobile: full-screen overlay with swipe navigation between key factors

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 8bcc49c7-34e5-448b-950d-71abb492b257

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch feat/key-factors-2nd-iteration

---

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 and usage tips.}

[github-actions]

🚀 Preview Environment

Your preview environment is ready!

Resource	Details
🌐 Preview URL	https://metaculus-pr-4470-feat-key-factors-2nd-iteration-preview.mtcl.cc
📦 Docker Image	ghcr.io/metaculus/metaculus:feat-key-factors-2nd-iteration-f46cb8c
🗄️ PostgreSQL	NeonDB branch preview/pr-4470-feat-key-factors-2nd-iteration
⚡ Redis	Fly Redis mtc-redis-pr-4470-feat-key-factors-2nd-iteration

Details

• Commit: f46cb8c256f8918f00e44de138952f7451d4847f
• Branch: feat/key-factors-2nd-iteration
• Fly App: metaculus-pr-4470-feat-key-factors-2nd-iteration

---

ℹ️ Preview Environment Info

Isolation:

• PostgreSQL and Redis are fully isolated from production
• Each PR gets its own database branch and Redis instance
• Changes pushed to this PR will trigger a new deployment

Limitations:

• Background workers and cron jobs are not deployed in preview environments
• If you need to test background jobs, use Heroku staging environments

Cleanup:

• This preview will be automatically destroyed when the PR is closed

[cemreinanc]

this feels like if comment is null, this can run on every re-render as ensureCommentLoaded function is also not wrapped in useCallback. Are we sure this line only sends api request once?