[cloud_firestore] add support for MetadataChanges

[long1eu]

Related Issues

flutter/flutter#16432

Checklist

Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

• I read the Contributor Guide and followed the process outlined there for submitting PRs.
• My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
• All existing and new tests are passing.
• I updated/added relevant documentation (doc comments with ///).
• The analyzer (flutter analyze) does not report any problems on my PR.
• I read and followed the Flutter Style Guide.
• The title of the PR starts with the name of the plugin surrounded by square brackets, e.g. [shared_preferences]
• I updated pubspec.yaml with an appropriate new version according to the pub versioning philosophy.
• I updated CHANGELOG.md to add a description of the change.
• I signed the CLA.
• I am willing to follow-up on review comments in a timely manner.

Breaking Change

Does your PR require plugin users to manually update their apps to accommodate your change?

• Yes, this is a breaking change (please indicate a breaking change in CHANGELOG.md and increment major revision).
• No, this is not a breaking change.

[long1eu]

It's a bit strange. I'm running pub global activate flutter_plugin_tools && pub global run flutter_plugin_tools format but I get a different result than the one from cirrus.

The difference was on the flutter version, I used the stable channel.

[collinjackson]

Thanks for the PR. This can be done more idiomatically in Dart using a boolean optional named argument. I've pushed a change to your PR.

This change needs an integration test in addition to the unit test.

[collinjackson]

Thanks for the PR! LGTM

[googlebot]

All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter.

We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only @googlebot I consent. in this pull request.

Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

[googlebot]

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

[long1eu]

Do you want me to fix this? Also please make sure to assign me 2 issues each week. I prefer the ones related to plugins. :D

[collinjackson]

I think I fixed the test. Do you have any feedback/changes you want to make before I merge this?

Generally we try prioritize PRs that are associated with issues that have a lot of thumbs. Feel free to reach out to me on Gitter or via my email [email protected] for advice on issue prioritization.

Here are some auth issues you might consider taking on:

• Is there any way to implement forgot password and send verification mail firebase flutter#12459
• Delete Firebase Auth User flutter#15907
• [plugins/firebase_auth] Access custom claims flutter#20238
• [plugins/firebase_auth] [plugins/cloud_firestore] custom claims not propagated on Android with user.getIdToken(refresh: true) flutter#22801
• firebase_auth plugin does not return the refresh_token and access token flutter#35974

[long1eu]

LGTM, also I can take flutter/flutter#35974

[collinjackson]

LGTM, also I can take flutter/flutter#35974

Great, thank you. I put a few other issue ideas in the list above.