feat(firebase_messaging)!: upgrade messaging web to Firebase v9 JS SDK. #8860
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
russellwheatley
added
the
platform: web
russellwheatley
changed the title
firebase_functions web to v9 SDK.
russellwheatley
changed the title
firebase_functions web to v9 SDK.
russellwheatley
changed the title
10 tasks
russellwheatley
changed the title
# Conflicts: # packages/firebase_core/firebase_core_web/lib/src/firebase_core_web.dart # packages/firebase_core/firebase_core_web/lib/src/interop/app.dart # packages/firebase_core/firebase_core_web/lib/src/interop/core_interop.dart # packages/firebase_database/firebase_database_web/lib/src/interop/app.dart
Salakar
approved these changes
Jul 6, 2022
Lyokone
approved these changes
Jul 7, 2022
russellwheatley
changed the title
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Breaking Change
isSupported()is a web API but is also on the method channel. It is now async so that API is now a Future which makes this a breaking change.Does your PR require plugin users to manually update their apps to accommodate your change?