-
Notifications
You must be signed in to change notification settings - Fork 4k
fix(messaging, web): Fix incorrect type casting. #12573
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
Conversation
@@ -8,6 +8,7 @@ | |||
import 'dart:async'; | |||
import 'dart:js_interop'; | |||
|
|||
import 'package:_flutterfire_internals/_flutterfire_internals.dart'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Why do we need this extra import?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Opps I was trying something, and forgot to delete it.
Hello, how to update this? Is already avaliable? |
* fix(messaging, web): Fix incorrect type casting. * formatting: remove unused import * formatting: change formatting
* fix(messaging, web): Fix incorrect type casting. * formatting: remove unused import * formatting: change formatting
* fix(messaging, web): Fix incorrect type casting. * formatting: remove unused import * formatting: change formatting
* fix(messaging, web): Fix incorrect type casting. * formatting: remove unused import * formatting: change formatting
* fix(messaging, web): Fix incorrect type casting. * formatting: remove unused import * formatting: change formatting
still getting the same issue |
Description
Fixes: #12572
Replace this paragraph with a description of what this PR is doing. If you're modifying existing behavior, describe the existing behavior, how this PR is changing it, and what motivated the change.
Related Issues
Replace this paragraph with a list of issues related to this PR from the issue database. Indicate, which of these issues are resolved or fixed by this PR. Note that you'll have to prefix the issue numbers with flutter/flutter#.
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.///
).melos run analyze
) does not report any problems on my PR.Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?