Skip to content

[cloud_firestore_platform_interface] Fix three-way merge in test file. #2209

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 20, 2020

Conversation

ditman
Copy link
Contributor

@ditman ditman commented Mar 20, 2020

Description

Even though my last push didn't have conflicts with the base branch (according to Github), there was a change that I missed:

4d7b2bd#diff-e36a6cd96b7ef43422dfb1197627e7f8

I fixed the same issue in my change, but deleting the OTHER 'source' key in the map:

bd9bcd4#diff-e36a6cd96b7ef43422dfb1197627e7f8

The result is now that the file has zero entries in said Map, and tests broke in master.

This commit reverts my part of the change, so tests pass again.

Related Issues

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.
  • If the pull request affects only one plugin, the PR title starts with the name of the plugin in brackets (e.g. [cloud_firestore])
  • 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.
  • 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?

  • No, this is not a breaking change.

Even though my last push didn't have conflicts with the base branch,
there was a change that I missed:

4d7b2bd#diff-e36a6cd96b7ef43422dfb1197627e7f8

I fixed the same issue in my change, but deleting the OTHER 'source' key
in the map:

bd9bcd4#diff-e36a6cd96b7ef43422dfb1197627e7f8

This commit reverts my part of the change, so tests pass again.
@ditman ditman merged commit d0318c1 into firebase:master Mar 20, 2020
@ditman
Copy link
Contributor Author

ditman commented Mar 20, 2020

(Merged to unbreak tree)

@ditman ditman deleted the fix-three-way-merge branch March 20, 2020 01:02
@firebase firebase locked and limited conversation to collaborators Aug 2, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants