Issue #1 is about a typical client/server graphQL implementation.
Here is an alternative, worth implementing in a different feature of this gradually sprawling example application:
Implement GraphQL entirely in the client code, talking to a REST backend. This should serve as a nice illustration of usefulness of GraphQL even in systems where the server-side API is already well-established.
This mode of operation is supported by GraphQL, no invention here, just digging around and wiring up the APIs inside an Angular application.
Relatively few organizations have a strong interest in this approach, so I'm going to set this aside and continue only on the GraphQL server-side path.
Issue #1 is about a typical client/server graphQL implementation.
Here is an alternative, worth implementing in a different feature of this gradually sprawling example application:
Implement GraphQL entirely in the client code, talking to a REST backend. This should serve as a nice illustration of usefulness of GraphQL even in systems where the server-side API is already well-established.
This mode of operation is supported by GraphQL, no invention here, just digging around and wiring up the APIs inside an Angular application.