mirror of
https://github.com/hasura/graphql-engine.git
synced 2025-01-07 08:13:18 +03:00
e7462f7884
<!-- The PR description should answer 2 important questions: --> ### What Trying to understand what is going on here. Still no closer, but have added a test and made some types more specific in order to clarify my understanding. <!-- What is this PR trying to accomplish (and why, if it's not obvious)? --> <!-- Consider: do we need to add a changelog entry? --> <!-- Does this PR introduce new validation that might break old builds? --> <!-- Consider: do we need to put new checks behind a flag? --> ### How Add some introspection tests for relationships with `ObjectBooleanExpressionType`s to ensure they generate. Tried to make relationship fields disappear to recreate build problems but could not. Split `BooleanExpressionGraphqlConfig` and `ObjectBooleanExpressionGraphqlConfig` to make sure we're not mixing them up. We only want to use `BooleanExpressionGraphqlConfig` in `metadata_resolve`, this ensures that. Pushed some partiality in `schema/boolean_expressions.rs` out - a function was `Option<inputs> -> Option<outputs>` and now it's `inputs -> outputs`. We use `Option` a lot and it makes reasoning why something hasn't been added to the schema difficult. <!-- How is it trying to accomplish it (what are the implementation steps)? --> V3_GIT_ORIGIN_REV_ID: 893e6f32bfded14ea724be7eaedc519e264f4c01 |
||
|---|---|---|
| .. | ||
| auth | ||
| custom-connector | ||
| engine | ||
| execute | ||
| ir | ||
| lang-graphql | ||
| metadata-resolve | ||
| metadata-schema-generator | ||
| open-dds | ||
| plugins/pre-execution-plugin | ||
| query-usage-analytics | ||
| schema | ||
| sql | ||
| utils | ||