# CHANGELOG

***

**NOTE:** This changelog is no longer maintained. Changes are now tracked in the top level [`CHANGELOG.md`](https://github.com/apollographql/apollo-client/blob/master/CHANGELOG.md).

***

### vNext

* Add support for arrays to `filter`. [PR #3591](https://github.com/apollographql/apollo-client/pull/3591)

### 4.1.14

* No changes.

### 4.1.13

* No changes.

### 4.1.12

* No new changes.

### 4.1.11

* Source files are now excluded when publishing to npm. [Issue #2806](https://github.com/apollographql/apollo-client/issues/2806) [PR #3454](https://github.com/apollographql/apollo-client/pull/3454)

### 4.1.10

* Fix [#3393](https://github.com/apollographql/apollo-client/issues/3393) [PR #3403](https://github.com/apollographql/apollo-client/pull/3403)

### 4.1.9

* Various optimizations for cache read performance [#3300](https://github.com/apollographql/apollo-client/pull/3300)

### 4.1.8

* Map coverage to original source

### 4.1.4

* dependency updates
* support null literal
* stop running the check function for a proptype check if the data is still loading

### 4.1.3

* update to latest apollo-utilities

### 4.1.2

* update to latest apollo-utilities

### 4.1.1

* package dependency updates

### 4.1.0

* add support for async resolution via `import { graphql } from 'graphql-anywhere/lib/async'` as an experimental way to do async resolvers

### 4.1.0-alpha.0

* add support for async resolution via `import { graphql } from 'graphql-anywhere/lib/async'` as an experimental way to do async resolvers

### 4.0.2

* package dependency updates

### 4.0.1

* Improved rollup builds

### 4.0.0

* Replace core utils with apollo-utilities
* Move to using lerna for the repo [PR #1984](https://github.com/apollographql/apollo-client/pull/1984)

### v3.1.0

* Add `directives` to the `info` argument, with information about all of the directives on the current field. [PR #52](https://github.com/apollographql/graphql-anywhere/pull/52) by [brysgo](https://github.com/brysgo) and [cesarsolorzano](https://github.com/cesarsolorzano)
* Merging overlapping fragment and inline object fields [PR #67](https://github.com/apollographql/graphql-anywhere/pull/67) by [abergenw](https://github.com/abergenw)

### v3.0.1

* Fix behavior of getMainDefinition to allow fragment definitions to precede the main operation definition

### v3.0.0

* Improve performance of getMainDefinition.
* Breaking: getMainDefiniton now returns first operation definition in document instead of query before mutation.

### v2.2.0

* Fix mishandling of arrays in fragments
* Operation definition can also be a mutation (instead of only query)

### v2.1.0

Tolerate missing variables (to support optional arguments) Remove a circular dependency

### v2.0.0

Change typings from `typed-graphql` to `@types/graphql`.

### v1.1.2

Remove dependency on lodash completely, so this package now has zero runtime dependencies. Nice!

### v1.1.1

Roll back failed update in 1.1.0

### v1.0.0

Releasing 0.3.0 as 1.0.0 in order to be explicit about Semantic Versioning.

### v0.3.0

Add a set of utilities for easily filtering objects with fragments and queries.

This is essentially the code that lived in <https://www.npmjs.com/package/graphql-fragments>

### v0.2.4

* Added support for fragments. If there are multiple fragments in the provided document, the first one is used as the query.

### v0.2.3

* Remove dep on lodash.isarray

### v0.2.2

* Add enum support

### v0.2.1

* Add context arg to `fragmentMatcher`.

### v0.2.0

* Change the last argument to `options`, move `resultMapper` there, and add `fragmentMatcher`.

### v0.1.x

* Changes were not tracker before this version.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.mediamagic.dev/product-docs/services/graphql-gateway/node_modules/graphql-anywhere/changelog.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.