graphql-engine/v3/crates
Daniel Harvey 0551a78246 Remove data connector-specific information from resolved ObjectBooleanExpressionType (#604)
<!-- Thank you for submitting this PR! :) -->

## Description

The new `BooleanExpressionType` for objects is not tied to a single data
connector. As we'll be attempting to compile both input kinds into the
same resolved metadata types, let's make sure we depend on this
information as little as possible.

Mostly this is absolutely fine, the only time we now use this
information (other than still checking it for user errors) is when
juggling relationships when generating GraphQL schema items for a
boolean expression. We will have to cross this bridge when we come to
it.

Functional no-op.

V3_GIT_ORIGIN_REV_ID: 9550217e253fb71df09251928ab9b30750617c9e
2024-05-22 09:28:54 +00:00
..
auth Bump schemars from 0.8.19 to 0.8.20 (#592) 2024-05-20 08:45:48 +00:00
custom-connector Add support for HTTP/2 to the custom connector. (#581) 2024-05-14 15:11:28 +00:00
engine No-op refactor routes related code in engine main.rs (#600) 2024-05-20 15:54:45 +00:00
execute Bump schemars from 0.8.19 to 0.8.20 (#592) 2024-05-20 08:45:48 +00:00
lang-graphql Bump schemars from 0.8.19 to 0.8.20 (#592) 2024-05-20 08:45:48 +00:00
metadata-resolve Remove data connector-specific information from resolved ObjectBooleanExpressionType (#604) 2024-05-22 09:28:54 +00:00
metadata-schema-generator Bump schemars from 0.8.19 to 0.8.20 (#592) 2024-05-20 08:45:48 +00:00
open-dds OpenDD types for new boolean expressions (#599) 2024-05-21 09:28:53 +00:00
schema Remove data connector-specific information from resolved ObjectBooleanExpressionType (#604) 2024-05-22 09:28:54 +00:00
utils [opendds-derive]: allow hiding enum variants from JSONSchema (#598) 2024-05-20 13:30:56 +00:00