mirror of
https://github.com/hasura/graphql-engine.git
synced 2024-12-22 15:01:39 +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 |
||
---|---|---|
.. | ||
author_article.yaml | ||
can_insert_in_insertable_view.yaml | ||
cannot_insert_in_non_insertable_view.yaml | ||
constraint_violation_mssql.yaml | ||
float_variable_mssql.yaml | ||
insert_integer_overflow_mssql.yaml | ||
insert_integer_overflow.yaml | ||
insert_into_array_col_with_array_input.yaml | ||
insert_invalid_datetime_mssql.yaml | ||
insert_multiple_objects_mssql.yaml | ||
insert_numeric_value_fail_mssql.yaml | ||
insert_table_no_pk_mssql.yaml | ||
insert_various_mssql_types.yaml | ||
insert_various_postgres_types.yaml | ||
order_col_shipped_null.yaml | ||
person_jsonb_array.yaml | ||
person_jsonb_variable_array.yaml | ||
person_jsonb_variable.yaml | ||
person_jsonb.yaml | ||
person_valid_variable_but_invalid_graphql_value.yaml | ||
schema_setup_mssql.yaml | ||
schema_setup.yaml | ||
schema_teardown_mssql.yaml | ||
schema_teardown.yaml | ||
setup_mssql.yaml | ||
teardown_mssql.yaml | ||
values_teardown_mssql.yaml | ||
values_teardown.yaml |