Right, that's a valid point. I did not realize it.
So let's implement this in GraphQL now...
The Camunda API here is:
These are the adapted GraphQL type definitions:
You can immediately see how they resemble the Camunda API.
Now having this above Type Definitions in place, we can rewrite our query nicely like this:
(see how we are getting closer to the Java API. Cherry-picking from the Camunda API...)
The query in GraphiQL looks now like this:
(I added the internal GraphQL field
to the query selector to show the GraphQL type: As you can see the query
returns correctly a list of
as an implementation of the interface
At least for the process instance queries we generalized the Type Schema using GraphQL interfaces to resemble the Camunda API.
The same must now be applied to the mutation
createProcessInstance, which I implement next...
(Maybe the same Pattern applies to tasks and other things...)
Again, thanks for your valid input here