Pometry / Pometry/Raphtory

Syntactic sugar for or/and filters

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

Nobody has claimed this yet.

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

Description

filter.Edge.src().property("p1") == "pometry" && filter.Edge.dst().property("p1") == "pometry"
Can this be rewritten succinctly?

filter.Edge.nodes().all().property("p1") == "pometry"
filter.Edge.nodes().any().property("p1") == "pometry"

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 filter API implementing Edge.src(), Edge.dst(), nodes(), all(), and any(); the issue provides the existing expressions and proposed shorthand. Determine the intended semantics and locate relevant tests. Done means the proposed syntactic sugar has agreed behavior and test coverage.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
database
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.