Distinct History Object for nodes and edges

Open arienandalibi opened this issue 8 months ago • 3 comments

What changes were proposed in this pull request?

The history object will take care of the history of nodes and edges. It will also implement different functionalities so they don't have to be implemented in Python by the user.

Why are the changes needed?

Improve user experience when dealing with histories by implementing useful features out of the box.

Does this PR introduce any user-facing change? If yes is this documented?

The history object itself, which will be documented

How was this patch tested?

Not been tested yet

Are there any further changes required?

Integration with Raphtory

Fixes #1424

May 05 '25 04:05 arienandalibi

All committers have signed the CLA.

May 05 '25 04:05 CLAassistant

How does this effect windowing with before(), at(), after(), window(), expand() and rolling() ?

Sep 29 '25 14:09 jbaross-pometry

Also on a naming convention question, why time no temporal here?

Sep 29 '25 15:09 jbaross-pometry