⚡ Bolt: Optimize export foreign key lookups by using parsed handles

[seonghobae]

💡 What: Precomputes a node-level Set of column names, decodes each ERD edge handle once with parseColumnNameFromHandle, and validates the decoded name with Set.has instead of scanning and re-encoding every column.

🎯 Why: FK export previously performed an O(C) column scan for each edge after decoding the handle, retaining avoidable CPU and allocation cost on large diagrams.

📊 Complexity: Column indexes are built once in O(N * C). Each edge performs bounded O(H) handle decoding plus O(1) average-case Set.has membership checks, eliminating the previous O(C) per-edge existence scan. String decoding itself is not claimed to be O(1).

🛡️ Correctness hardening:

• malformed hexadecimal tokens such as src-c-0069junk-0064 are rejected rather than partially parsed;
• invalid Unicode code points are rejected;
• the supported c-empty encoding is preserved without falling through to placeholder FK columns;
• focused regression tests prove the old per-edge Array.some scan is no longer used.

✅ Verification on head abc57fd38bb7a66abac826942311900a2c847f50:

• fail-first predecessor head 23816da4eaad968914d762f203b7446afad7c942 deterministically failed all three new focused regressions for the intended pre-fix behavior;
• current pull-request CI reports frontend typecheck, 204 tests, production build, backend checks, Security Scan, and Semgrep successful;
• CodeRabbit status is successful and all inline review threads are resolved.

⚠️ Merge evidence caveat: the repository's current pull-request CI checks out GitHub's synthetic merge ref rather than the literal PR head. Under the repository's exact-head policy, those successful synthetic-merge runs are useful regression evidence but are not sufficient merge evidence. Independent non-author current-head approval is also still required.

---

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

Summary by CodeRabbit

• 개선 사항
  • ERD에서 외래 키 컬럼을 더 빠르고 정확하게 식별합니다.
  • 인코딩된 핸들에서 컬럼명을 안정적으로 복원하고, 실제 존재하는 컬럼만 외래 키로 표시합니다.
  • 잘못된 형식이나 비어 있는 값도 안전하게 처리합니다.

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

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 42 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

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: 99625255-b5d5-46cf-b5c4-34019a1b00df

📥 Commits

Reviewing files that changed from the base of the PR and between 80fc839 and 37adca6.

📒 Files selected for processing (5)

• .jules/sentinel.md
• frontend/src/erd/__tests__/handleLookupRegression.test.ts
• frontend/src/erd/export.ts
• frontend/src/erd/handleUtils.test.ts
• frontend/src/erd/handleUtils.ts

📝 Walkthrough

Walkthrough

핸들 ID에서 컬럼명을 직접 복원하는 parseColumnNameFromHandle을 추가했습니다. FK 엣지 내보내기는 디코딩된 컬럼이 노드에 존재할 때 이를 사용하고, 그렇지 않으면 기존 fallback을 사용합니다. 파서 동작 테스트도 추가했습니다.

Changes

FK 핸들 디코딩

Layer / File(s)	Summary
핸들 파서와 검증 frontend/src/erd/handleUtils.ts, frontend/src/erd/handleUtils.test.ts	src- 및 tgt- 핸들에서 컬럼명을 복원하는 parseColumnNameFromHandle을 추가했습니다. 빈 입력, 잘못된 형식, 잘못된 인코딩의 반환값을 테스트합니다.
FK 내보내기 통합 frontend/src/erd/export.ts, .jules/bolt.md	FK 엣지 처리에서 핸들 ID를 직접 파싱합니다. 복원된 컬럼이 노드에 존재할 때 사용하고, 유효하지 않으면 기존 PK 기반 fallback을 사용합니다. 최적화 지침을 추가했습니다.

Estimated code review effort: 2 (Simple) | ~10 minutes

Possibly related PRs

• ContextualWisdomLab/pg-erd-cloud#663: 동일하게 핸들 디코딩으로 FK 엣지 컬럼을 해석합니다.
• ContextualWisdomLab/pg-erd-cloud#668: 핸들 파서와 FK 컬럼 해석 로직을 함께 변경합니다.
• ContextualWisdomLab/pg-erd-cloud#700: ERD 내보내기에서 핸들 ID를 컬럼명으로 디코딩합니다.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
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.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	제목은 export의 외래 키 조회를 파싱된 핸들로 최적화하는 주요 변경 사항을 명확하고 간결하게 설명합니다.

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch jules-perf-handle-lookup-14142744112914767576

---

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

[coderabbitai]

Actionable comments posted: 4

🤖 Prompt for all review comments with AI agents

Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.jules/bolt.md:
- Around line 80-82: 엣지별 노드 컬럼 확인이 현재 .some 순회로 선형 탐색을 수행하므로 설명의 O(1) 주장과 구현이
일치하지 않습니다. FK 엣지 조회 로직에서 컬럼명을 담은 Set 인덱스를 먼저 구성하고, 각 조회가 해당 Set을 사용하도록 변경하십시오.
인덱스를 추가하지 않는 경우에는 선형 존재 확인이 유지된다는 내용으로 복잡도 설명을 갱신하십시오.

In `@frontend/src/erd/export.ts`:
- Around line 75-84: The edge-processing logic in frontend/src/erd/export.ts
lines 75-84 must replace per-edge columns.some checks with node-level Set
indexes built before the edge loop, then validate parsed source and target
columns using Set.has for O(1) lookup. Update .jules/bolt.md lines 80-82 to
document O(1) column lookup only after this Set-based indexing is implemented.
- Around line 75-88: Update the source and target handle checks in
fkColumnsForEdge to accept empty column names by testing parsedSource and
parsedTarget against null rather than truthiness, and use !== undefined for the
final resolved-column existence checks. Add focused fkColumnsForEdge tests
covering c-empty handles and preserving fallback behavior when handles cannot be
resolved.

In `@frontend/src/erd/handleUtils.ts`:
- Around line 33-40: Update the decoding logic around the visible split/map flow
in handleUtils so every token is validated as a complete hexadecimal code point
before calling parseInt; reject any token containing non-hex characters by
returning null, while preserving valid decoding and existing error handling. Add
a focused test covering encoded input such as src-c-0069junk-0064 and assert
that decoding returns null.

🪄 Autofix

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 039ce735-14df-4d2f-9c62-0da4c045d3f0

📥 Commits

Reviewing files that changed from the base of the PR and between 72afe6d and 80fc839.

⛔ Files ignored due to path filters (1)

• frontend/pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

📒 Files selected for processing (4)

• .jules/bolt.md
• frontend/src/erd/export.ts
• frontend/src/erd/handleUtils.test.ts
• frontend/src/erd/handleUtils.ts