Graph config needs more work
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 642
- Forks
- 70
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 21
Description
- All the config should be defaulted based on the config file for the GraphQL server
- Improve the override on load such that you don't need to specify everything (currently anything unspecified is reset to default) (Resolved in https://github.com/Pometry/Raphtory/pull/2688)
- Make it more obvious that segment sizes cannot be overridden on load (Resolved in https://github.com/Pometry/Raphtory/pull/2688)
More changes discussed:
- Modify graphql to pass config through constructors
- Only persist config passed into
new; do not persist configs passed in throughload- Follow up: Expose API to change the config on already created graphs
- Allow graph config to be set through config file (similar to
ServerArgsinraphtory-graphql)
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 tracing the GraphQL configuration flow and the constructors that currently receive graph configuration, then compare it with ServerArgs in raphtory-graphql. Review the config-file behavior and the load path, including the resolved changes in pull request 2688. Done means the remaining checklist items have an agreed API and consistent persistence behavior for new, loaded, and already-created graphs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- graphql, rust
- Domain
- api, databases
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100