-
After some discussion, it would be nice to reiterate that GraphQL's partial results can be useful to provide two distinct behaviors. Namely, running transactional requests and _batching_ requests.
…
-
It would be really nice to be able to have types for inputs and results for `graphql-client` and it feels like it just requires gluing together some existing pieces of code.
A file of graphql queri…
-
Creation of a GraphQL plugin that is aware of the syntax and semantics of a GraphQL client call (the provider response is standard JSON over HTTP).
Whilst GraphQL is currently supported by Pact (see …
-
In our Sourcegraph clients that aren't served from the same origin as the API (browser extension, VS Code extension), we make requests from the background and forward responses to the client in order …
-
Currently, the `LoggingInterceptor` does not work with graphql. Internal calls to `intercept`, `logNext`, and `logError` use the base `ExecutionContext` from nest without first evaluating the [curren…
-
Hi, I discovered that Issues counter is not comparable with real issues listed in GitHub web UI.
This is, as you probably know, not an API issue, but rather a feature. It returns open issues and PRs …
-
### Expected Behavior
expected the variables element in the JSON request to be an object with the variables
`--data '{"query":"query test($id: [String!]!) {\n login {\n service(id: $id) {\n …
-
Test API as a user
-
# Step 1/5 - Create a git branch
- Create a branch called `feature/setup-graphql`
If you don't remember how to create a branch, check the references in the previous issues.
**Note**: From here, the…
-
Seeing this error message:
```
otel-collector_1 | 2022-08-20T22:03:26.430Z error prometheusexporter@v0.58.0/accumulator.go:105 failed to translate metric {"kind": "exporter", "data_type": "metrics"…