Improve the graph filtering implementation for plugins
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 642
- Forks
- 70
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 21
Description
We probably should be pushing the graph down to the auth extension for processing rather than pushing the filter up to keep this logic more self-contained.
Originally posted by @ljeub-pometry in https://github.com/Pometry/Raphtory/pull/2731#discussion_r3870760593
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the graph filtering implementation and the auth extension involved in the discussion linked from PR 2731. Determine how filtering is currently pushed upward and what interface would let the extension process the graph; done means the logic is self-contained in the extension without changing filtering behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- backend, databases
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100