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
..
architecture.md	Split metadata-resolve into own crate (#543)	2024-05-02 12:29:22 +00:00
roles-and-annotations.md	Format everything with Prettier. (#530)	2024-04-30 14:58:57 +00:00