Nullsafety support

[aliyazdi75]

flutter pub get:

Because every version of flutter_localizations from sdk depends on intl 0.17.0-nullsafety.2 and dart_json_mapper 1.7.2 depends on intl ^0.16.1, flutter_localizations from sdk is incompatible with dart_json_mapper 1.7.2.
And because no versions of dart_json_mapper match >1.7.2 <2.0.0, flutter_localizations from sdk is incompatible with dart_json_mapper ^1.7.2.
So, because  depends on both dart_json_mapper ^1.7.2 and flutter_localizations any from sdk, version solving failed.

[aliyazdi75]

It can be fixed by adding:

dependency_overrides:
  intl: ^0.17.0-nullsafety.2

[k-paxian]

At the moment I'm doing exactly that.
reflectable package is not migrated yet, as soon it'll happens I'll proceed with the migration

[mit-mit]

Null safety support in reflectable is tracked in google/reflectable.dart#229

[jiechic]

At the moment I'm doing exactly that.
reflectable package is not migrated yet, as soon it'll happens I'll proceed with the migration

it is update reflectable 3.0.0-nullsafety.1

[k-paxian]

It should be stable, 3.0.0 otherwise it's not ready. At this moment it's only a preview of partial migration.

[cedvdb]

stable has been released, v3.0.0 although I don't see the null-safety label the PR says it's for null safety google/reflectable.dart#237

Prepare a release as 3.0.0 (not 3.0.0-nullsafety.X), that is, a stable release with null safety support.

[k-paxian]

Mapper has been migrated to null safety 🥇, but..., due to this issue, pub.dev doesn't recognize that yet 😞 we are still waiting for the wonder.

[mapleafgo]

Hope to provide nullsafety support for dart_json_mapper_mobx

[k-paxian]

@mapleafgo ok, I thought no one is using it really

[mapleafgo]

@mapleafgo ok, I thought no one is using it really

It's a very useful tool.

[buzzware]

Still waiting for this, even though https://pub.dev/packages/reflectable/changelog says
"3.0.0 Support null safety in a stable version of reflectable."
This is the last thing holding up my app from null safety.

[k-paxian]

@buzzware According to this issue all the blame could be addressed towards maintainers of build_runner_core which is Google 😄

[buzzware]

@buzzware According to this issue all the blame could be addressed towards maintainers of build_runner_core which is Google 😄

OK, thanks, I'll draw their attention to it

[k-paxian]

[buzzware]

Yay! Thanks to all involved. I just got back to this :)