Skip to content

Refactor Graph edge key storage to use JSON serialization#7

Merged
saurabhsharma2u merged 1 commit intomainfrom
fix-fragile-edge-keys-16326270772881790958
Feb 25, 2026
Merged

Refactor Graph edge key storage to use JSON serialization#7
saurabhsharma2u merged 1 commit intomainfrom
fix-fragile-edge-keys-16326270772881790958

Conversation

@saurabhsharma2u
Copy link
Copy Markdown
Contributor

This PR addresses a code health issue in plugins/core/src/graph/graph.ts where edge keys were constructed using a simple pipe | delimiter. This was fragile because URLs containing | would break the key parsing logic.

The fix involves:

  1. Encapsulating edge key creation and parsing into static methods Graph.getEdgeKey and Graph.parseEdgeKey.
  2. Using JSON.stringify([source, target]) as the key format, which safely handles any character in URLs.
  3. Updating all references in Graph class and duplicate.ts to use these new methods.
  4. Refactoring duplicate.test.ts to avoid manual key construction, improving test robustness.

Verification:

  • Ran vitest for plugins/core including duplicate.test.ts, metrics.test.ts, and crawler.test.ts.
  • Ran vitest for plugins/cli to ensure no regressions in downstream usage.
  • Verified manual edge key generation script output.

PR created automatically by Jules for task 16326270772881790958 started by @saurabhsharma2u

- Introduced `Graph.getEdgeKey` and `Graph.parseEdgeKey` to encapsulate edge key generation logic.
- Replaced `|` delimiter with `JSON.stringify` to ensure robustness against delimiter collisions in URLs.
- Updated `Graph` methods `addEdge`, `getEdges`, and `fromJSON` to use the new key management methods.
- Refactored `plugins/core/src/graph/duplicate.ts` to use the new `Graph` static methods for edge processing.
- Updated `plugins/core/tests/duplicate.test.ts` to use `graph.addEdge` and `Graph.getEdgeKey`, removing fragile manual string concatenation.
@google-labs-jules
Copy link
Copy Markdown

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

@saurabhsharma2u saurabhsharma2u marked this pull request as ready for review February 25, 2026 14:32
@saurabhsharma2u saurabhsharma2u merged commit 0b833df into main Feb 25, 2026
6 checks passed
@saurabhsharma2u saurabhsharma2u deleted the fix-fragile-edge-keys-16326270772881790958 branch February 25, 2026 14:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant