Auke Booij 6ac67a5566 Allow collecting metadata dependencies and inconsistencies separately ... `CollectedInfo` was just an awkward sum type. By using an explicit `Either` instead, we can guarantee at the type level that certain methods only write inconsistencies, or only write dependencies. This is useful, because if we can guarantee that no dependencies are written, then we don't need to run `resolveDependencies` on that part of the Metadata. In other words, we can keep it out of `BuildOutputs`, which greatly benefits performance - see e.g. hasura/graphql-engine-mono#6613. PR-URL: https://github.com/hasura/graphql-engine-mono/pull/6765 GitOrigin-RevId: 9ce099d2eee2278dbb6e5bea72063e4b6e064b35		2022-11-15 17:00:11 +00:00
..
IR	ghc 9.2.5	2022-11-15 11:26:42 +00:00
Types	Allow collecting metadata dependencies and inconsistencies separately	2022-11-15 17:00:11 +00:00
MetadataSpec.hs	Add Cockroach and Postgres to DataValidation tests	2022-10-27 12:20:41 +00:00
PermissionSpec.hs	server, pro: actually reformat the code-base using ormolu	2021-09-23 22:57:37 +00:00
WebhookTransformsSpec.hs	server: Rework internal webhook request transform components	2022-03-23 20:24:44 +00:00