-
Notifications
You must be signed in to change notification settings - Fork 4.1k
refactor(firebase_database): firebase_database_platform_interface #6668
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
refactor(firebase_database): firebase_database_platform_interface #6668
Conversation
|
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA). 📝 Please visit https://cla.developers.google.com/ to sign. Once you've signed (or fixed any issues), please reply here with What to do if you already signed the CLAIndividual signers
Corporate signers
ℹ️ Googlers: Go here for more info. |
|
@googlebot I signed it! |
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.
if we make this enum (EventType) public (which is not required for now) then need to update the event string in native sides also. Should I make this EventType enum public?
|
@Salakar I have submitted this pull request which will create a separate firebase_platform_database_reference and federate the firebase_database. |
|
check all_plugins / analyze (pull_request) is failing because I have used the path dependency of |
# Conflicts: # packages/firebase_database/firebase_database/pubspec.yaml
lesnitsky
left a comment
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.
all comments are related to the code which was moved around, not authored by the @deepak786, so not sure if that should be of his concern. @Salakar thoughts?
...ase/firebase_database_platform_interface/lib/src/method_channel/method_channel_database.dart
Outdated
Show resolved
Hide resolved
...se_database_platform_interface/lib/src/method_channel/method_channel_database_reference.dart
Show resolved
Hide resolved
...se_database_platform_interface/lib/src/method_channel/method_channel_database_reference.dart
Show resolved
Hide resolved
...se_database_platform_interface/lib/src/method_channel/method_channel_database_reference.dart
Show resolved
Hide resolved
...se_database_platform_interface/lib/src/method_channel/method_channel_database_reference.dart
Outdated
Show resolved
Hide resolved
...se_database_platform_interface/lib/src/method_channel/method_channel_database_reference.dart
Outdated
Show resolved
Hide resolved
...tabase/firebase_database_platform_interface/lib/src/method_channel/method_channel_query.dart
Outdated
Show resolved
Hide resolved
...tabase/firebase_database_platform_interface/lib/src/method_channel/method_channel_query.dart
Outdated
Show resolved
Hide resolved
...firebase_database/firebase_database_platform_interface/lib/src/platform_interface/query.dart
Outdated
Show resolved
Hide resolved
|
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
|
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
|
|
|
All (the pull request submitter and all commit authors) CLAs are signed, but one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that by leaving a comment that contains only Note to project maintainer: There may be cases where the author cannot leave a comment, or the comment is not properly detected as consent. In those cases, you can manually confirm consent of the commit author(s), and set the ℹ️ Googlers: Go here for more info. |
|
@deepak786 would you be willing to give your consent for co-authoring this? I've fixed my comments myself 😉 |
|
@googlebot I consent. |
|
@googlebot I consent. |
|
@lesnitsky is that you asked? |
|
@deepak786 yes, thanks |
Description
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?