⚡ Bolt: 최적화 ERD 핸들 ID 생성 성능 개선

[seonghobae]

💡 What: sanitizeHandleId 함수에서 사용하던 Array.from()과 .join() 체인을 네이티브 for 루프로 교체하여 중간 배열 할당을 제거했습니다. 코드에 최적화 이유를 명시하는 주석을 추가했습니다.
🎯 Why: 프론트엔드 ERD 그래프 처리 과정에서 핫 패스로 작용하는 부분으로, 불필요한 가비지 컬렉션(GC) 오버헤드와 배열 생성 비용을 줄이기 위함입니다.
📊 Measured Improvement: 10만 번 반복 벤치마크 기준 기존 약 776ms에서 331ms로 실행 시간 개선을 확인했습니다.
🔬 Measurement: pnpm test를 통해 유니코드 및 이모지 처리가 기존과 동일하게 동작하는지 확인 완료했습니다.

---

PR created automatically by Jules for task 7575747546827823674 started by @seonghobae

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

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 13 minutes

Limit details: You’ve used all 1 included review currently available under your plan.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

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: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 6b9eadef-b8ec-4ba9-b4c9-9519849caa60

📥 Commits

Reviewing files that changed from the base of the PR and between 466e616 and 58c1adf.

📒 Files selected for processing (1)

• frontend/src/erd/handleUtils.ts

---

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

[seonghobae]

@opencode-agent review

Please review exact current head 58c1adf. Re-evaluate this head only; do not transfer predecessor approvals or check evidence.

[seonghobae]

Closing as superseded by #937. Current-head comparison shows the same production sanitizeHandleId optimization (Unicode-safe native loop, equivalent c-empty behavior); #937 also carries the matching Bolt worklog. No unique production files or tests are present in #919.

[google-labs-jules]

Closing as superseded by #937. Current-head comparison shows the same production sanitizeHandleId optimization (Unicode-safe native loop, equivalent c-empty behavior); #937 also carries the matching Bolt worklog. No unique production files or tests are present in #919.

Understood. Acknowledging that this work is now superseded by #937 and stopping work on this task.