Changelog
1.8.3
readFragment
types to allow | {}
optional fragments to be matched. When a fragment is annotated with a directive making it optional (such as @include
, @skip
, or @defer
) then its typed as optional. readFragment
previously didn't know how to match these types, but it will now match T | {}
and infer the type as such
Submitted by @kitten (See #349)Changelog
1.8.0
@defer
, @skip
, and @include
optional fragments causing types to become exponentially more complex to evaluate, causing a recursive type error. Instead, merging field types and sub-selections from fragments is now separated, as needed
Submitted by @kitten (See #319)