Daniel Harvey 11240e2bff 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 12:29:22 +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	Split metadata-resolve into own crate (#543)	2024-05-02 12:29:22 +00:00
lang-graphql	Refactor errors, and split execute and explain code path (#525)	2024-05-02 07:29:06 +00:00
metadata-resolve	Split metadata-resolve into own crate (#543)	2024-05-02 12:29:22 +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