Skip to content
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

fix(firestore, web): fix a query error in Flutter Web that was affecting the parsing of ancient dates #9633

Merged
merged 1 commit into from
Oct 4, 2022

Conversation

Lyokone
Copy link
Contributor

@Lyokone Lyokone commented Sep 29, 2022

Description

Instead of going through DateTime, which was causing errors, I'm going directly to the Timestamp class (which is the intended final class). Removing the DateTime step removes the error.

Related Issues

Fixes #7230

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. Updating the pubspec.yaml and changelogs is not required.

  • 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 (melos run analyze) does not report any problems on my PR.
  • I read and followed the Flutter Style Guide.
  • 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.
  • No, this is not a breaking change.

@@ -23,8 +24,7 @@ dynamic dartify(Object? jsObject) {
return object;
}
if (util.instanceof(object, TimestampJsConstructor)) {
return DateTime.fromMillisecondsSinceEpoch(
(object as TimestampJsImpl).toMillis());
return Timestamp((object as TimestampJsImpl).seconds, object.nanoseconds);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Does that mean what used to be decoded as a DateTime is now decoded as a Timestamp? If so, that could be a breaking change

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We were previously decoding it as follow TimestampJS => DateTime => Timestamp
Now we only do TimestampJS => Timestamp

So no breaking change :)

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it would also show up in the e2e tests if it was a problem

@Lyokone Lyokone merged commit 9250d45 into master Oct 4, 2022
@Lyokone Lyokone deleted the fix/7230 branch October 4, 2022 09:23
@firebase firebase locked and limited conversation to collaborators Nov 4, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

🐛 [cloud_firestore] Query error in Flutter for Web because of ancient dates
4 participants