graphql-engine/v3/crates/plan
Daniel Harvey bec9dee021 Move argument presets resolve into metadata-resolve (#1226)
<!-- The PR description should answer 2 important questions: -->

### What

Previously we were doing the business of calculating which arguments
(and parts of arguments) were preset in the GraphQL `schema` crate. This
meant we would have to reimplement the logic for each backend. Now we
move it into `metadata-resolve` so the results can be shared by all
frontends.

### How

Move argument preset resolve into `metadata-resolve`. What's left in
`graphql-schema` is all the stuff relating to `Annotation`s of various
kinds.

A lot of the diff is changing `ModelWithPermissions` and
`CommandWithPermissions` to `ModelWithArgumentPresets` and
`CommandWithArgumentPresets` in crates after `metadata-resolve`.

Functional no-op.

V3_GIT_ORIGIN_REV_ID: b1b0983abb9f6282652c8689b02e0796026752f5
2024-10-15 14:16:26 +00:00
..
src Move argument presets resolve into metadata-resolve (#1226) 2024-10-15 14:16:26 +00:00
Cargo.toml Move commands from sql to plan (#1188) 2024-10-03 10:28:39 +00:00
README.md Create plan crate (#1149) 2024-09-24 14:40:11 +00:00

plan

the crate where we turn OpenDD IR + resolved metadata into execute::plan types. Kept separate from other crates because this is likely to be a mess to begin with.