Fix warnings for Flutter 3.0 - Warning: Operand of null-aware operation '!' has type 'SchedulerBinding' which excludes null.

[fzyzcjy]

Detailed warnings:

    ../../../../.pub-cache/git/charts-30477090290b348ed3101bc13017aae465f59017/charts_flutter/lib/src/chart_container.dart:249:27: Warning: Operand of null-aware operation '!' has type 'SchedulerBinding' which excludes null.
     - 'SchedulerBinding' is from 'package:flutter/src/scheduler/binding.dart' ('../../../../fvm/versions/3.0.0/packages/flutter/lib/src/scheduler/binding.dart').
        if (!SchedulerBinding.instance!.hasScheduledFrame) {
                              ^
    ../../../../.pub-cache/git/charts-30477090290b348ed3101bc13017aae465f59017/charts_flutter/lib/src/chart_container.dart:250:24: Warning: Operand of null-aware operation '!' has type 'SchedulerBinding' which excludes null.
     - 'SchedulerBinding' is from 'package:flutter/src/scheduler/binding.dart' ('../../../../fvm/versions/3.0.0/packages/flutter/lib/src/scheduler/binding.dart').
          SchedulerBinding.instance!.scheduleFrame();
                           ^
    ../../../../.pub-cache/git/charts-30477090290b348ed3101bc13017aae465f59017/charts_flutter/lib/src/chart_container.dart:253:22: Warning: Operand of null-aware operation '!' has type 'SchedulerBinding' which excludes null.
     - 'SchedulerBinding' is from 'package:flutter/src/scheduler/binding.dart' ('../../../../fvm/versions/3.0.0/packages/flutter/lib/src/scheduler/binding.dart').
        SchedulerBinding.instance!.addPostFrameCallback(startAnimationController);
                         ^
    ../../../../.pub-cache/git/charts-30477090290b348ed3101bc13017aae465f59017/charts_flutter/lib/src/chart_container.dart:276:22: Warning: Operand of null-aware operation '!' has type 'SchedulerBinding' which excludes null.
     - 'SchedulerBinding' is from 'package:flutter/src/scheduler/binding.dart' ('../../../../fvm/versions/3.0.0/packages/flutter/lib/src/scheduler/binding.dart').
        SchedulerBinding.instance!.addPostFrameCallback(doRebuild);

fix #771

[viralkachhadiya]

@fzyzcjy one more file need to be fix https://github.com/google/charts/blob/master/charts_flutter/example/lib/behaviors/slider.dart
line no.122

[fzyzcjy]

done

[viralkachhadiya]

must be specify limit new flutter version 3.0.0 in pubspec.yml otherwise those who are not using latest version of 3.0.0, they all are getting error. #764

[fzyzcjy]

done

[rickcasson]

To maintain compatibility while removing warnings, I would recommend using the approach suggested in the Flutter 3.0 release notes: https://docs.flutter.dev/development/tools/sdk/release-notes/release-notes-3.0.0#your-code

[viralkachhadiya]

@rickcasson can you close this pr? Bcz @fzyzcjy might be not available and assign me .

[fzyzcjy]

Oh I forgot it. Let me update it.

[fzyzcjy]

done

[ilovelinux]

Fix #771

[fzyzcjy]

Any updates...?

[lohanbodevan]

Hey @rickcasson, any idea when it would be released? Thanks ;)

[rickcasson]

@lohanbodevan @fzyzcjy, sorry, no idea. I'm not a maintainer of this repo, and based on the readme, it doesn't sound like they are accepting external contributions anyway...

[blong-sofi]

@google-admin , @google-ospo-team , gentle bump

[google-admin]

@google/google-charts-admins can maybe help

[marceloamp2]

Same issue

[a15056478]

Did anyone find any other solution for this? @google-admin

[robinpdev]

looks awesome, comments are clear. Would be nice if this got approved

[gfb-47]

Would be nice if this got approved

[a15056478]

Looks good

[filippo-veneri]

PR is OK

[tushar0518]

@nshahan can you please look into it? Thank you.

[jatinArhamLabs]

@rickcasson when this branch gets merged

[DanOxlade]

+1 for this, this is the last package my app needs to be updated for Flutter 3+

[ilovelinux]

@DanOxlade you can already upgrade to Flutter 3+. The library does its job, the only annoying thing is a little warning (not error, see PR description) you will get every time you will build an app.

[gfb-47]

pr is fine, what is the issue?

[stuartmorgan]

This project is no longer maintained, and cannot accept any PRs. Community members interested in collaborating on a community-maintained fork can coordinate in this issue.