feat(core, windows): Add api to access firebase cpp objects #11254
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
cynthiajoan
changed the title
Lyokone
approved these changes
Jul 11, 2023
| return App::GetInstance(appName.c_str()); | ||
| } | ||
|
|
||
| void *FirebaseCorePlugin::GetFirebaseAuth(std::string appName) { |
There was a problem hiding this comment.
It makes me think that auth will probably need a tenantId parameter but I don't think this is available yet on C++.
There was a problem hiding this comment.
what is the purpose of tenantId? I'd like to see how to map that into the c++ lib.
There was a problem hiding this comment.
It is used to determine the tenant of the app: https://cloud.google.com/identity-platform/docs/multi-tenancy
russellwheatley
approved these changes
Jul 11, 2023
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
Add apis to firebase_core windows to access firebase cpp object like App*, Auth* etc.
Related Issues
N/A
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?