Observable dependency not null safe

[lejard-h]

The only dependency not null safe.

It seems the migration is over on the github repo of the package, but not publish on pub

google/observable#107

During migration we can rely on the github version of the package, but we'll probably need to fork it and publish it ourself.

[jodinathan]

I am thinking in clone the observable repo, make some adjustments like removing deprecated stuff and publishing with a new name to pub.dev.
What do you guys think?

[jodinathan]

@GZGavinZhao

[GZGavinZhao]

@jodinathan I'm OK with that. Call it ngobservable?

[jodinathan]

I was thinking in call it change_notifier and have an async version, which Angular uses, and a sync version that is basically extracted from Flutter core.

[GZGavinZhao]

That sounds good! I forked it to the organization. You can create a PR to it.

[jodinathan]

created the PR and published to pub: https://pub.dev/packages/change_notifier.

@GZGavinZhao was this the only issue stoping us from migrating the files?
if yes, is the null-safety branch ready to start migrating?

lets roll :D