feat(remote_config, web): migrate web to js_interop to be compatible with WASM #12489
Conversation
This file contains hidden or 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
13 tasks
Lyokone
changed the title
exaby73
approved these changes
Mar 15, 2024
russellwheatley
approved these changes
Mar 19, 2024
guide-loclt
pushed a commit
to guide-inc-org/guide-flutter_fire
that referenced
this pull request
Apr 5, 2024
…with WASM (firebase#12489) * feat(analytics, web): migrate web to js_interop to be compatible with WASM * fix version
guide-loclt
pushed a commit
to guide-inc-org/guide-flutter_fire
that referenced
this pull request
Apr 5, 2024
…with WASM (firebase#12489) * feat(analytics, web): migrate web to js_interop to be compatible with WASM * fix version
guide-loclt
pushed a commit
to guide-inc-org/guide-flutter_fire
that referenced
this pull request
Apr 5, 2024
…with WASM (firebase#12489) * feat(analytics, web): migrate web to js_interop to be compatible with WASM * fix version
guide-loclt
pushed a commit
to guide-inc-org/guide-flutter_fire
that referenced
this pull request
Apr 5, 2024
…with WASM (firebase#12489) * feat(analytics, web): migrate web to js_interop to be compatible with WASM * fix version
guide-loclt
pushed a commit
to guide-inc-org/guide-flutter_fire
that referenced
this pull request
Apr 16, 2024
…with WASM (firebase#12489) * feat(analytics, web): migrate web to js_interop to be compatible with WASM * fix version
guide-loclt
pushed a commit
to guide-inc-org/guide-flutter_fire
that referenced
this pull request
Apr 16, 2024
…with WASM (firebase#12489) * feat(analytics, web): migrate web to js_interop to be compatible with WASM * fix version
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
3 participants
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
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
#12466
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.yamland 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?