|
Ran
|
Files
17
|
Run time
1s
|
Badge
README BADGES
|
push
travis-ci
<a href="https://github.com/apollographql/graphql-tools/commit/<a class=hub.com/apollographql/graphql-tools/commit/22d2295d037e32b81bdc2937ab40f97539adca74">22d2295d0<a href="https://github.com/apollographql/graphql-tools/commit/22d2295d037e32b81bdc2937ab40f97539adca74">">Also recreate astNode for fields (#580) * Also recreate astNode for fields In a [previous commit](https://github.com/apollographql/graphql-tools/commit/</a><a class="double-link" href="https://github.com/apollographql/graphql-tools/commit/<a class="double-link" href="https://github.com/apollographql/graphql-tools/commit/fd9f6260faa779b2bfc12f1f707cdf2b778d306b">fd9f6260f</a>">fd9f6260f</a><a href="https://github.com/apollographql/graphql-tools/commit/22d2295d037e32b81bdc2937ab40f97539adca74">) we added the `astNode` property in the `reacreateCompositeType` function. That resulted in cache control working with schema stitching but only for GraphQL Types. By recreating the `astNode` prop also in `fieldToFieldConfig` cache control also works for fields. This is required for caching fields and hence queries. * Add ast to input field node too
579 of 655 branches covered (88.4%)
1141 of 1208 relevant lines covered (94.45%)
96.29 hits per line
| Coverage | ∆ | File | Lines | Relevant | Covered | Missed | Hits/Line | Branch Hits | Branch Misses |
|---|