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
..
Control	server: Share tests between CircularT and MemoizeT.	2022-09-08 19:38:49 +00:00
Data	scaffolding for remote-schemas module	2022-10-21 03:15:04 +00:00
Database/MSSQL	Source catalog migrations minor enhancements	2022-11-01 22:42:40 +00:00
Hasura	Allow collecting metadata dependencies and inconsistencies separately	2022-11-15 17:00:11 +00:00
Network/HTTP/Client	Upgrade Ormolu to v0.5.	2022-11-02 20:55:13 +00:00
Test	[server]: feature flag to remove _stream fields from schema	2022-11-04 13:10:35 +00:00
Discover.hs	Use hspec-discover for src-test, remove unitSpecs list.	2022-07-18 14:15:17 +00:00
Main.hs	Install and use ODBC Driver 18 for SQL Server (msodbcsql18).	2022-10-21 16:25:04 +00:00