Property API fixes
Open
@shivamka1 is already working on this.
Since Jun 18, 2025.
Semantics/API
- Dominant language
- Rust
- Stars
- 642
- Forks
- 70
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 21
Description
This is a master ticket to jot down annoying things with the property API's
- #2014
- If you ask for properties on edges/nodes and all of the entities do not have this property you will get a None, if some of them do you will get an iterator of Options - this means you have to check fi the returned object is None, instead of just being about to iterate over an empty iterator.
- If I call get on an individual Node/Edge I will get a None if that entity doesn't have that property (understandable), but I will also get Nones when calling on Edges/Nodes - this means that I can only call sum() etc when all Edges/Nodes have this property. As we know the type of the property (assuming at least one entity has it) it makes much more sense to return a default value i.e. 0, "", or []
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.