Filtering todos

[shivamka1]

The apply_views function should just go away and be replaced by filter once the filter apis are feature-complete and cover all these cases!

Originally posted by @ljeub-pometry in #2350 (comment)

[shivamka1]

the filter_nodes and filter_edges functions should be combined (same as in rust)

Originally posted by @ljeub-pometry in #2350 (comment)

[shivamka1]

ids is redundant with the select (also we need to remember to fix the select filter for nodes (right now it applies a subgraph filter which can remove too many nodes if they were only added via edges, can you make sure there is a ticket for this?)

Originally posted by @ljeub-pometry in #2350 (comment)

[shivamka1]

Replace this with TimeIndexComponent when merged from master.

Originally posted by @shivamka1 in #2359 (comment)

[shivamka1]

PyNodeWindow/EdgeWindow/ExplodedEdgeWindow can probably be replaced with dynamic dispatch eventually but it is a bit more tricky

Originally posted by @ljeub-pometry in #2359 (comment)

[shivamka1]

not for now, but the GraphQL side structure is nicer than the internal rust representation, maybe we can change that in the future

Originally posted by @ljeub-pometry in #2311 (comment)

[shivamka1]

Maybe we should make this a special method since this is being used to add a node list without other filters a lot!

Originally posted by @ljeub-pometry in #2364 (comment)

[shivamka1]

We probably want to make apply take a NodeStorageRef as the only input.

Originally posted by @ljeub-pometry in #2364 (comment)

[shivamka1]

New issues to add:

• Add support for comparison operations to LazyNodeState/NodeOp
• Add CreateFilter implementation for LazyNodeState/NodeState where the value type is bool

Originally posted by @ljeub-pometry in #2364 (comment)

[shivamka1]

Should any and all also be list aggregations instead of something special. I.e., if property "x" is e.g. List(I64), the syntax would be something like
(filter.Node.property("x") == 1).any()
instead of
filter.Node.property("x").any() == 1
and any and all should be supported for other List(Bool) properties, e.g.,
filter.Node.property("y").all()
where property "y" is of type List(Bool).

Originally posted by @ljeub-pometry in #2294