Fix struct hierarchy in graphql
Open
@ljeub-pometry is already working on this.
Since Dec 4, 2025.
GraphQL
- Dominant language
- Rust
- Stars
- 642
- Forks
- 70
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 21
Description
Currently have several different structs for managing folders in Graphql -Namespace, ExistingGraphFolder, ValidGraphFolder, GraphFolder - need to review these and make sure all are needed and use eachother appropriately.
- Would be good to rethink how we do Graph/Namespace validation - quite a bit of duplicated code and would be ideal if the structs themselves done the validating so that we can be sure they are safe.
fn Pathin Namesapce should not need to return an option - Namespace should have validated the path- We should store the relative path as a string within the namespace so that we know it is always validated and we don't have to replace \ with / everywhere for example.
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.
Assessment
This issue has not been assessed yet.