Expose Firebase App and Firestore database to public

[ibilux]

The Firebase App and Firestore database are/maybe needed for some other work.
It's better to expose Firebase App and Firestore database to public.

[AshleyMedway]

This will work fine for the web implementation but the Android and iOS implementations will return JSON objects that match the serializable properties of the Swift/Java objects. What's the extra work that is needed? Probably we should add more methods to the implementation?

[ibilux]

The Firebase App and Firestore database are need for the Firebase packages (like auth).
So it's better to expose them as public.
I used the JSON objects as return for Android and iOS implementations, because i thought this package used JSON objects as a return as a common rule.
If the JSON objects is not needed as a return type, it should be removed.

[AshleyMedway]

What I mean is that the App and Firestore are classes. i.e. Firestore is often cast to FirebaseAppImpl within the firebase codeset. So you wouldn't be able to pass the firestore returned from Android/iOS into another call?

[ibilux]

@AshleyMedway The Capacitor Android Plugin Guide indicate that the resolve() method of PluginCall takes a JSObject and supports JSON-serializable data types.
So this mean it can return a FirebaseAppImpl or any other object type,
But you are right this doesn't mean it will work.
If it didn't work we will need to implement something like @capacitor-firebase/app.

[AshleyMedway]

Yeah I think how they’ve done it might be the way, return the config and create the same objects in the web, however, the general idea for this plugin is to remove the need for the web versions all together due to their flaky-ness particularly on iOS