You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Apr 4, 2023. It is now read-only.
I might be missing something but if I understand correctly, the Android's Gradle file and iOS' Podfile are created and configured during the npm postinstall step.
I find this a bit annoying for the two following reasons:
Everyone in the team who installs the project will be prompted for configuring the firebase plugin.
A CI build would also be prompted.
Wouldn't there be a way to have a configuration file that could be added to a version control system and the npm postinstall script would first try to read that config file and do the prompting only if it does not already exist ?
The text was updated successfully, but these errors were encountered:
acramatte
changed the title
version control firebase add-on services ?
Version control firebase add-on services ?
Aug 22, 2016
acramatte
changed the title
Version control firebase add-on services ?
Version control firebase add-on services configuration?
Aug 22, 2016
Sounds useful.. perhaps we can copy it to App_Resources and use that if it exists. BUT what if the install script changes? Then we need to detect that and rerun it (and write it to App_Resources again).
I'm sure that can be automated but let's first discuss this a little. Pinging @sean-perkins since he's the hero that added the script.
Hi,
I might be missing something but if I understand correctly, the Android's Gradle file and iOS' Podfile are created and configured during the npm postinstall step.
I find this a bit annoying for the two following reasons:
Wouldn't there be a way to have a configuration file that could be added to a version control system and the npm postinstall script would first try to read that config file and do the prompting only if it does not already exist ?
The text was updated successfully, but these errors were encountered: