[ifmelate]

3.4.0: add_id_fields, and moving over from Artemis or graphql_codegen

add_id_fields: true

Selects id on every object type and interface with a scalar id, the way __typename is added, in the sent documents and the result classes (in unions, inside ... on Type).

Without id, package:graphql's normalized cache keeps an object only inside the result that returned it. Checked with a fake server that returns only the selected fields:

	without the option	with it
mutation rename { name }, then read another query of that user	old name	new name
read<Fragment>Fragment({'id': '2'}) for an object a query returned	null	the data

Documents stay valid:

• A selection where another field is aliased id (directly, in an inline fragment or in a spread fragment) doesn't get id. If a fragment spread there would get id itself, the build fails with the new BLD109.
• Types that share a union or interface with a type whose id has another type (ID! vs Int!) get no id.

Both rules depend only on the schema and the fragment definitions, so a fragment has the same fields in fragments.dart and in every operation. Rewritten documents were checked with graphql-js validate.

The README said a missing id could cause CacheMissException. That doesn't happen with package:graphql 5.2, so the README now describes what does go wrong.

scalar_mapping with from_json / to_json

Two top-level functions, the way Artemis and graphql_codegen configure scalars. types.dart wraps them in a <Scalar>FunctionsConverter. Works in both result modes, for _-prefixed scalars (Hasura's _text), for built-in scalars, and for functions with nullable types.

dart run flutter_graphql_codegen:migrate

Writes graphql_codegen.yaml from the Artemis or graphql_codegen options in build.yaml: schema, documents, output, scalars with their functions (Artemis coercers as defined in the parser file), enums, widgets and hooks. It lists what it can't carry over and stops on several schemas.

Checked on the Artemis graphbrainz and graphql_codegen example projects: both build with this generator, analyze clean, and their scalars go through their own functions both ways.

MIGRATION.md has "Coming from Artemis" and "Coming from graphql_codegen", with the names side by side. The names were checked against the code their examples generate.

Checks

• dart test: 434 tests pass, including the compile-tagged ones.
• dart analyze --fatal-infos: no issues.
• dart format --set-exit-if-changed: no changes.
• dart pub publish --dry-run: 0 warnings.