Schematics, schematics, schematics!

[jamesdaniels]

• Allow selection of a particular Firebase Hosting Site from ng add
• Allow creation of a new Firebase Project, Hosting Site, or Application from the ng add command
• Fetch the application configuration object from ng add
• ng add prompts for Node version, prerendering, and allows for deployment to Cloud Run
• ng deploy allow configuration of the function name How to change the name of cloud function name while working with Multiple angular SSR hosting in same project as the function name is default to SSR? #2825 and deploy to Cloud Run
• cleaning up the dist paths for Cloud Functions wrong output path for deploy #2780 so you can do a manual deploy
• don't fail deploy if index.html doesn't exist SSR + i18n ENOENT: no such file or directory, rename index.html -> index.original.html #2765
• accept serverTarget (in addition to the legacy universalBuildTarget) to conform with current conventions ng deploy - allow configuration for serverTarget #2764
• fix bundleDependencies in server deploys, the default should be true rather than false
• mark all firebase cli calls as nonInteractive
• make sure we're using tokens on all deploy permutations
• drying up some of the deploy logic
• add all accepted configuration params to the schema
• allow prerendering only option, rather than deploying to Cloud Functions / Run
• removing the installed dependencies in favor of global firebase-tools and proper deps Document usage of Angularfire dev dependencies #2840
• ng add will now import the Firebase feature modules and environment config you select, feat(schematics): ng-add schematics #1853
• ng add will add firebase files to your .gitignore, Feature request: ng add @angular/fire should add hosting cache to .gitignore #2828

TODO

• Allow non-standard browser/server dist paths
• Allow override of functions/run dist path
• Check for gcloud cli
• Get tests green and cover
• Can we query Google's repository to validate Node.js version rather than docker hub?
• tidy/dry up
• write the environment config
• allow addition of modules to the app.module
• better handle conflicts / merging of config
• add .firebase/ and logs to .gitignore
• allow basic configuration of the Cloud Run instance
• default to all the prior defaults, e.g, ng deploy will succeed on an 7.0.4 app

[googlebot]

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 @googlebot I consent. in this pull request.

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 cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

[googlebot]

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

[google-cla]

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

[googlebot]

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 @googlebot I consent. in this pull request.

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 cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

[google-cla]

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 @googlebot I consent. in this pull request.

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 cla label to yes (if enabled on your project).

ℹ️ Googlers: Go here for more info.

[google-cla]

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

[googlebot]

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.