mirror of
https://github.com/hasura/graphql-engine.git
synced 2024-12-17 12:31:52 +03:00
20cbe9cfd3
Introspection queries accept variables, but we need to make sure to also touch the variables that we ignore, so that an introspection query is marked not reusable if we are not able to build a correct query plan for it. A better solution here would be to deal with such unused variables correctly, so that more introspection queries become reusable. An even better solution would be to type-safely track *how* to reuse which variables, rather than to split the reusage marking from the planning. Co-authored-by: Tirumarai Selvan <tiru@hasura.io> |
||
|---|---|---|
| .. | ||
| agg_perm | ||
| aggregations | ||
| allowlist | ||
| basic | ||
| boolexp | ||
| caching | ||
| computed_fields | ||
| custom_schema | ||
| enums | ||
| functions | ||
| limits | ||
| offset | ||
| order_by | ||
| permissions | ||
| v1alpha1/errors | ||