Pometry / Pometry/Raphtory

Deduplicate props in raphtory APIs

Open
#2,112 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Enhancement
Dominant language
Rust
Stars
642
Forks
70
Avg merge
2d 13h
Merged PRs (30d)
21

Description

Right now props are vec everywhere which means there could be even duplicates requiring to check duplicates everywhere. We should probably change the input at the high level to reject duplicates.

https://github.com/Pometry/Raphtory/pull/2103#discussion_r2121033702

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with the discussion on PR #2103, then trace the Raphtory APIs that accept props as vectors. Determine the intended high-level rejection behavior for duplicate properties and identify the affected call paths. Done means duplicate props are rejected consistently rather than requiring duplicate checks throughout the codebase.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
databases
Issue type
Refactor
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.