Nullsafe gql, gql_exec, gql_link

[micimize]

This is a first pass at a nullsafe gql, mostly done with dart migrate and applied quick fixes. Idk what the status of nnbd-gql is – this was basically a "follow the instructions and see if tests pass" approach.

[micimize]

Null safety migrations run thus far:

Libraries

• cats
• gql
• gql_exec
• gql_link
• gql_http_link
• gql_dedupe_link
• gql_error_link
• gql_transform_link
• gql_websocket_link
• gql_dio_link

blocked by dart-lang/build#2920

• gql_code_builder
• gql_build

Examples

• gql_example_cli
• gql_example_cli_github
• gql_example_build
• gql_example_http_auth_link
• gql_example_dio_link
• gql_example_flutter

[klavs]

Great work!
I can see this deployed as the initial nnbd version.
But before the final nnbd version is deployed, gql AST must be rechecked manually with GraphQL spec at hand. I know there are some fields on AST classes which are non-nullable and some are nullable.

I kind of forgot about the dart migrate when I did my initial work on nnbd (in some other branch)

[micimize]

migrated gql_http_link – discovered two things:

• We'll have to wait on build_runner for the build packages Add support for nullsafety dart-lang/build#2920
• Tests with mockito will have to add some code gen, and not add the autogenerated ! assertions in tests.

I'm thinking I should actually merge this into a gql-dart:nullsafety branch here and publish -nullsafety.alpha.0 versions manually as they're ready

[klavs]

I'm thinking I should actually merge this into a gql-dart:nullsafety branch here and publish -nullsafety.alpha.0 versions manually as they're ready

I thought about the same thing because of the auto-release.

[klavs]

Almost every single use of ! operator is a potential for a bug :(

[klavs]

This is probably a bug as well.