Executing a graphqlOperation only returns a Promise and not Observabe

Describe the bug Looking at the type definition of API.graphql I see that it either returns Promise<GraphQLResult> or Observable<object>.

However, when I look at the code returned from a query I see a Promise:

Now I always have to do a ugly promise conversion, for example:

 return from<Promise<{ data: { getPosts: GetPostQuery[] } }>>(API.graphql(
      graphqlOperation(statement, args))
    )
      .pipe(
        map(response => response.data.getPosts)
      ) as Observable<GetPostQuery[]>;

Any chance Observable (RXJS and not Zen) can be used?

[rob3c]

I agree with the OP that rxjs should replace zen for the observable implementation 👍

While it may seem obvious that promises should be used for requests that only return single values and observables should be used for those that stream multiple values over time, that’s not necessarily the case.

The reason that libraries like angular use observables instead of promises for even simple http requests that will only every return single values (like the queries and mutations mentioned above), is that they make canceling the requests trivial. This also normally aborts the http request’s connection in addition to just leaving it alive and ignoring the result, which is a nice optimization to get for free. Standard promise implementations do not support cancellation, which makes things like typeahead searches, request timeouts and other request-related logic much harder to implement efficiently.

[mattiLeBlanc]

It would also be nice to support generics <T> so that we can set our return type.