mirror of
https://github.com/hasura/graphql-engine.git
synced 2024-12-18 04:51:35 +03:00
6e8da71ece
(Work here originally done by awjchen, rebased and fixed up for merge by jberryman) This is part of a merge train towards GHC 9.2 compatibility. The main issue is the use of the new abstract `KeyMap` in 2.0. See: https://hackage.haskell.org/package/aeson-2.0.3.0/changelog Alex's original work is here: #4305 BEHAVIOR CHANGE NOTE: This change causes a different arbitrary ordering of serialized Json, for example during metadata export. CLI users care about this in particular, and so we need to call it out as a _behavior change_ as we did in v2.5.0. The good news though is that after this change ordering should be more stable (alphabetical key order). See: https://hasurahq.slack.com/archives/C01M20G1YRW/p1654012632634389 PR-URL: https://github.com/hasura/graphql-engine-mono/pull/4611 Co-authored-by: awjchen <13142944+awjchen@users.noreply.github.com> GitOrigin-RevId: 700265162c782739b2bb88300ee3cda3819b2e87 |
||
|---|---|---|
| .. | ||
| alter_column.yaml | ||
| column_field_swap.yaml | ||
| conflict_with_relationship.yaml | ||
| fail_conflicting_custom_table_name.yaml | ||
| relationship_conflict_with_custom_column.yaml | ||
| rename_original_table_with_custom_name.yaml | ||
| rename_original_table_with_identifier.yaml | ||
| set_and_unset.yaml | ||
| set_invalid_table.yaml | ||
| setup.yaml | ||
| teardown.yaml | ||
| use_deprecated_custom_column_names.yaml | ||