Make graphql-anywhere filter function generic #3929
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
A common part of many GraphQL/TypeScript setups is automatically generating TypeScript typings for any queries/mutations/fragments in the source code. For example, at Trialspark, we're using graphql-code-generator.
It would be great to more easily leverage the interfaces that tool is generating for our GraphQL fragments when using the
filter()
function from graphql-anywhere.This PR makes
filter()
generic on two, optional type arguments. The first represents the filtered data that is returned; the second represents the larger superset of data that is passed. This way, we can pass the autogenerated typings for our fragments to thefilter()
s that use those fragments: