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): update setSettings to allow usage of a up-to-date persistence on web #12041

Merged
merged 5 commits into from
Jan 16, 2024

Conversation

Lyokone
Copy link
Contributor

@Lyokone Lyokone commented Dec 15, 2023

Description

see title

Related Issues

fixes #12034

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.

@Lyokone Lyokone marked this pull request as ready for review December 28, 2023 08:31
@Lyokone Lyokone changed the title fix(firestore, web): replace deprecated usage of enablePersistence fix(firestore, web): update setSettings to allow usage of a up-to-date persistence on web Dec 28, 2023
Comment on lines +185 to +192
external PersistentSingleTabManager persistentSingleTabManager(
PersistentSingleTabManagerSettings? settings,
);

@JS()
external PersistentMultipleTabManager persistentMultipleTabManager(
PersistentSingleTabManagerSettings? settings,
);
Copy link
Member

Choose a reason for hiding this comment

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

Is the aim to allow these in the future? (along with memoryEagerGarbageCollector() & memoryLruGarbageCollector())

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes we probably need to refactor the front facing API to expose those APIs. I have to draft the API Review

@Lyokone Lyokone merged commit c917433 into master Jan 16, 2024
24 of 25 checks passed
@Lyokone Lyokone deleted the fix/12034 branch January 16, 2024 09:13
} else {
cacheSizeBytes = settings.cacheSizeBytes;
localCache = firestore_interop

Choose a reason for hiding this comment

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

After deprecation of enablePersistence we no longer have an API to specify multiple tab behavior on Web. So, which tab manager will be used by default when I set persistenceEnabled: true on Web?

@firebase firebase locked and limited conversation to collaborators Feb 16, 2024
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] Use of deprecated enableMultiTabIndexedDbPersistence() API on Web
4 participants