graphql-engine/v3/crates
Daniel Harvey 3f74f2e93d Move annotation type back into metadata resolve (#540)
<!-- Thank you for submitting this PR! :) -->

## Description

We'd like to split metadata resolve into it's own crate to enforce
module boundaries better. In doing so, discovered that it's using a type
from the later schema stage called `PredicateRelationshipAnnotation`,
which isn't really an annotation type at all, just a data structure for
a resolved predicate.

This moves that types back into metadata resolve, renaming it to
`PredicateRelationshipInfo`.

Functional no-op.

V3_GIT_ORIGIN_REV_ID: 5b37ca77fb4ddf17093277e6727360d6077c4e06
2024-05-02 09:17:41 +00:00
..
auth create auth and utils subdirectories in crates, and move architecture information to a separate doc. (#534) 2024-05-01 09:05:15 +00:00
custom-connector support field presets for input types (#454) 2024-04-23 15:02:04 +00:00
engine Move annotation type back into metadata resolve (#540) 2024-05-02 09:17:41 +00:00
lang-graphql Refactor errors, and split execute and explain code path (#525) 2024-05-02 07:29:06 +00:00
metadata-schema-generator All benchmarks must be Criterion benchmarks. (#498) 2024-04-23 13:00:24 +00:00
open-dds create auth and utils subdirectories in crates, and move architecture information to a separate doc. (#534) 2024-05-01 09:05:15 +00:00
utils create auth and utils subdirectories in crates, and move architecture information to a separate doc. (#534) 2024-05-01 09:05:15 +00:00