Samir Talwar 1a052dd44b server: Avoid partial fields wherever possible. ... This turns on the `partial-fields` warning, which yells at you if you try and create fields on sum types that end up being partial functions. These are dangerous; we had a bug because we introduced a new case to a data type, making the field accessors partial, and leading to a crash in certain cases. This means that we have introduced a few wrappers in various places where the field names are useful, but we want to avoid partial matches. Unfortunately this can be turned off by prefixing the field name with an underscore. Ideally we would try and avoid exporting any field names with underscores, but lenses make this hard. I have removed some underscores for the areas in which we've seen this break in the past. We will have to be vigilant. [NDAT-794]: https://hasurahq.atlassian.net/browse/NDAT-794?atlOrigin=eyJpIjoiNWRkNTljNzYxNjVmNDY3MDlhMDU5Y2ZhYzA5YTRkZjUiLCJwIjoiZ2l0aHViLWNvbS1KU1cifQ PR-URL: https://github.com/hasura/graphql-engine-mono/pull/9991 GitOrigin-RevId: fd69b1ef999682969f3507f0e97513f983da4da6		2023-07-28 10:54:24 +00:00
..
Database/MSSQL	server: Avoid partial fields wherever possible.	2023-07-28 10:54:24 +00:00
Hasura/Backends/MSSQL	server: Split the integration tests out into their own directories.	2022-11-17 12:56:26 +00:00
Main.hs	server: Split the integration tests out into their own directories.	2022-11-17 12:56:26 +00:00
SpecHook.hs	server: Split the integration tests out into their own directories.	2022-11-17 12:56:26 +00:00