hasura/graphql-engine
1
0
Fork 0
mirror of https://github.com/hasura/graphql-engine.git synced 2024-12-15 01:12:56 +03:00
Code Issues Projects Releases Wiki Activity
247eebb118
graphql-engine/v3/crates/metadata-resolve/Cargo.toml

Ignoring revisions in .git-blame-ignore-revs. Click here to bypass and see the normal blame view.

34 lines
769 B
TOML
Raw Normal View History

Split `metadata-resolve` into own crate (#543) <!-- Thank you for submitting this PR! :) --> ## Description Now that metadata resolve has a clear interface with the rest of the engine, let's take it out into it's own crate. This will make it easier to maintain a strong boundary between things. To simplify imports etc, removed nested layers of modules, so now we import `use metadata_resolve::Qualified` instead of `use crate::metadata::resolved::Qualified`. The changes in `engine` crate are all just updating imports. Functional no-op. V3_GIT_ORIGIN_REV_ID: fb94304f7ed8883287c18bd6870045dfd69e3fe3
2024-05-02 15:28:27 +03:00
[package]
name = "metadata-resolve"
version.workspace = true
edition.workspace = true
license.workspace = true
[lib]
bench = false
[dependencies]
hasura-authn-core = { path = "../auth/hasura-authn-core" }
lang-graphql = { path = "../lang-graphql" }
open-dds = { path = "../open-dds" }
derive_more = "0.99.17"
indexmap = { version = "2", features = ["serde"] }
lazy_static = "1.4.0"
Aggregates Root Field - Part 2: Metadata Resolve (#684) This is Part 2 in a stacked PR set that delivers aggregate root field support. * Part 1: OpenDD: https://github.com/hasura/v3-engine/pull/683 * Part 3: GraphQL API: https://github.com/hasura/v3-engine/pull/685 JIRA: [V3ENGINE-159](https://hasurahq.atlassian.net/browse/V3ENGINE-159) ## Description This PR implements the metadata resolve phase of the engine and adds support for resolving `AggregateExpression`s and validates their use when linked to a `Model`. The bulk of the changes can be found in: * `crates/metadata-resolve/src/stages/aggregates/*` - This is where the `AggregateExpression`s are resolved * `crates/metadata-resolve/src/stages/models/mod.rs` - This is where we validate the `AggregateExpression` specified for use in the model is actually compatible with the model and its data connector The `ndc-spec` version used has been lifted to the latest version that adds support for aggregates over nested objects (https://github.com/hasura/ndc-spec/pull/144). This necessitated changes in the Custom Connector, but actual functionality to implement aggregation over nested objects is implemented in Part 3. There are also some changes in `crates/metadata-resolve/src/types/subgraph.rs` where the `Display` trait for the various `Qualified<T>`, `QualifiedTypeReference`, etc types has been reworked so that they print more cleanly, with the subgraph being put outside the type syntax, and array types getting formatted correctly. For example, previous an array of Varchars would have printed as `Varchar (in subgraph default)!`, now it properly formats as `[Varchar!]! (in subgraph default)`. This was necessary to make useful error messages using these types. A tonne of tests have been added in `crates/engine/tests/validate_metadata_artifacts/aggregate_expressions` to test every error condition of the metadata resolve process. [V3ENGINE-159]: https://hasurahq.atlassian.net/browse/V3ENGINE-159?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ V3_GIT_ORIGIN_REV_ID: ffd859127a3f1560707f06ef01906c9d1b183d31
2024-06-12 11:29:38 +03:00
ndc-models = { git = "https://github.com/hasura/ndc-spec.git", rev = "aa8ad48e42aefd9e585a4c923bebfd56eee40204" }
Split `metadata-resolve` into own crate (#543) <!-- Thank you for submitting this PR! :) --> ## Description Now that metadata resolve has a clear interface with the rest of the engine, let's take it out into it's own crate. This will make it easier to maintain a strong boundary between things. To simplify imports etc, removed nested layers of modules, so now we import `use metadata_resolve::Qualified` instead of `use crate::metadata::resolved::Qualified`. The changes in `engine` crate are all just updating imports. Functional no-op. V3_GIT_ORIGIN_REV_ID: fb94304f7ed8883287c18bd6870045dfd69e3fe3
2024-05-02 15:28:27 +03:00
nonempty = "0.10"
use a newtype for data connector object type (#542) ## Description Introduce a newtype for data connector object type for the added context. V3_GIT_ORIGIN_REV_ID: b499d3a9cd2610fec05a4bc2e1b3cf522f198b9c
2024-05-03 12:32:28 +03:00
ref-cast = "1.0"
Split `metadata-resolve` into own crate (#543) <!-- Thank you for submitting this PR! :) --> ## Description Now that metadata resolve has a clear interface with the rest of the engine, let's take it out into it's own crate. This will make it easier to maintain a strong boundary between things. To simplify imports etc, removed nested layers of modules, so now we import `use metadata_resolve::Qualified` instead of `use crate::metadata::resolved::Qualified`. The changes in `engine` crate are all just updating imports. Functional no-op. V3_GIT_ORIGIN_REV_ID: fb94304f7ed8883287c18bd6870045dfd69e3fe3
2024-05-02 15:28:27 +03:00
reqwest = { version = "0.11", features = ["json", "multipart"] }
Bump serde from 1.0.202 to 1.0.203 (#687) Bumps [serde](https://github.com/serde-rs/serde) from 1.0.202 to 1.0.203. V3_GIT_ORIGIN_REV_ID: 81b23526c9a289d401260350b8169907eb322bbf
2024-06-10 09:25:22 +03:00
serde = "1.0.203"
Bump serde_json from 1.0.115 to 1.0.116 (#553) V3_GIT_ORIGIN_REV_ID: 8ca39537cca63e86b1a350f484c351093418467f
2024-05-07 11:57:37 +03:00
serde_json = "1.0.116"
Split `metadata-resolve` into own crate (#543) <!-- Thank you for submitting this PR! :) --> ## Description Now that metadata resolve has a clear interface with the rest of the engine, let's take it out into it's own crate. This will make it easier to maintain a strong boundary between things. To simplify imports etc, removed nested layers of modules, so now we import `use metadata_resolve::Qualified` instead of `use crate::metadata::resolved::Qualified`. The changes in `engine` crate are all just updating imports. Functional no-op. V3_GIT_ORIGIN_REV_ID: fb94304f7ed8883287c18bd6870045dfd69e3fe3
2024-05-02 15:28:27 +03:00
thiserror = "1.0"
url = "2.4.1"
OpenDD types for new boolean expressions (#599) <!-- Thank you for submitting this PR! :) --> ## Description We have a new `BooleanExpressionType` metadata kind. This adds it, tests it can be parsed, but hides it from generated metadata and throws an error if one is actually used in the engine. V3_GIT_ORIGIN_REV_ID: 036b5fd9c32475d1c5a5e5e6321fb736fe6caefa
2024-05-21 12:28:02 +03:00
[dev-dependencies]
test-each = "*"
anyhow = "*"
similar-asserts = "*"
Split `metadata-resolve` into own crate (#543) <!-- Thank you for submitting this PR! :) --> ## Description Now that metadata resolve has a clear interface with the rest of the engine, let's take it out into it's own crate. This will make it easier to maintain a strong boundary between things. To simplify imports etc, removed nested layers of modules, so now we import `use metadata_resolve::Qualified` instead of `use crate::metadata::resolved::Qualified`. The changes in `engine` crate are all just updating imports. Functional no-op. V3_GIT_ORIGIN_REV_ID: fb94304f7ed8883287c18bd6870045dfd69e3fe3
2024-05-02 15:28:27 +03:00
[lints]
workspace = true
Reference in New Issue Copy Permalink