Mathias Klippinge

**Is your feature request related to a problem? Please describe.** Investigating #1356 closer, I have realized that it wouldn't be possible to increment the existing counter for queries that fail...

Plugin type unexpectedly gives app context instead of initial context

1

**Describe the bug** When writing plugins and using certain lifecycle methods you may get tricked into thinking context building has been done and will have app context available to you...

Supply a test that has a type issue

2

## Description Nothing is fixed, this is a failing (type) check highlighting the issue Related #1346 ## Type of change Please delete options that are not relevant.

feat(wrap): New transform AddArgumentsAsVariables

2

## Description Bring AddArgumentsAsVariables back from the grave, where it has been buried since v7.1.5 Related #4290 ## Type of change Please delete options that are not relevant. - [...

**Is your feature request related to a problem? Please describe.** Version 7.1.5 and earlier had a useful transform `AddArgumentsAsVariables`, which was removed, apparantly without a good replacement. **Describe the solution...

Marking a query field argument as no longer mandatory is considered a breaking change

1

Graphql Inspector says that: `✖ Type for argument transactions on field Query.transactions changed from [TransactionIdentifier!]! to [TransactionIdentifier!]` **To Reproduce** Checked in schema: ```ts const Schema = gql` type Query {...

There is a FIXME in `src/gateway/http.js` ```js // FIXME: Deprecated API // eslint-disable-next-line n/no-deprecated-api const defaults = url.parse(this.request.url()) ``` However, `url.parse(this.request.url())` is not equal to `new URL(this.request.url())`. So changing this...

In the fetch method (still not typed) the constructor of response is called with `Buffer` or `ArrayBuffer` in case the `fetchResponse` is binary. This was overlooked when typing Response. So...

Mappersmith partial match is not very easy to parse and identify why something is not matching

1

```shell "[Mappersmith Test] No exact match found for \"POST http://example.org/blogs\" (body: \"{\"title\":\"title\",\"data\":{\"nestedItemTwo\":2,\"nestedItemOne\":1,\"nestingLevelTwo\":{\"deepNestedItemTwo\":2,\"deepNestedItemOne\":1}}}\"; headers: \"\"), partial match with \"POST http://example.org/blogs\" (body: \"{\"title\":\"title\",\"data\":{\"nestedItemOne\":1,\"nestedItemTwo\":2,\"nestingLevelTwo\":{\"deepNestedItemOne\":1,\"deepNestedItemTwo\":2}}}\"; headers: \"\"), check your mock definition" ``` What I...

The dev dependency `@babel/register` is set to `