GraphQL mutation apis - Githubissues

ljeub-pometry commented 1 month ago

What changes were proposed in this pull request?

Add support for creating and mutating graphs using GraphQL

Graph Functions

[x] graph.add_node()
[x] graph.add_edge()
[x] graph.delete_edge()
[x] graph.add_properties()
[x] graph.add_constant_properties()
[x] graph.window.subgraph.etc.export_to("path/for/other/graph/")

Node functions

[x] graph.node.add_updates()
[x] graph.node.add_constant_properties()
[x] graph.node.update_constant_properties()

Edge functions

[x] graph.edge.add_updates()
[x] graph.edge.delete()
[x] graph.edge.add_constant_properties()
[x] graph.edge.update_constant_properties()

Why are the changes needed?

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

How was this patch tested?

Issues

_If this resolves any issues, please link to them here, the format is a KEYWORD followed by @__ KEYWORDS available are close, closes, closed, fix, fixes, fixed, resolve, resolves, resolved. Please delete this text before creating your PR

Are there any further changes required?

miratepuffin commented 1 month ago

Random stuff I have found

[x] If there is an invalid graph/file within your working directory on startup the sever won't start - perhaps should just skip the file and log a warning
[x] new_graph function gives "IO operation failed" when graph already exists - should be 'Graph already exists'
[x] new_graph function currently doesn't handle parent dirs correctly.
[x] If we delete all graphs in a namespace, do we want to also delete the namespace?
[x] When creating a new RaphtoryClient, it doesn't check the given URL, meaning an error is only thrown when you run your first query
[x] props needs to be properties to keep it inline with the python apis
[x] props in bulk updates need to be optional
[x] "Field \"addNode\" of type \"GqlMutableNode\" must have a selection of subfields"