Fixed issue where firebase init hosting re-prompts for source (#8617)

* Fixed issue where firebase init hosting re-prompts for source

* Simplify and correct condition for determining when to prompt

---------

Co-authored-by: joehan <[email protected]>

Author: aalej

CHANGELOG.md

@@ -1 +1,2 @@
+- Fixed issue where, with `webframeworks` enabled, `firebase init hosting` re-prompts users for source. (#8587)
 - Update typescript version in functions template to avoid build issue with @google-cloud/storage depedency (#8194)

src/init/features/hosting/index.ts

@@ -66,7 +66,7 @@ export async function doSetup(setup: any, config: any, options: Options): Promis
   if (experiments.isEnabled("webframeworks")) {
     if (discoveredFramework) {
       const name = WebFrameworks[discoveredFramework.framework].name;
-      setup.hosting.useDiscoveredFramework = await confirm({
+      setup.hosting.useDiscoveredFramework ??= await confirm({
         message: `Detected an existing ${name} codebase in the current directory, should we use this?`,
         default: true,
       });
@@ -82,7 +82,7 @@ export async function doSetup(setup: any, config: any, options: Options): Promis
   }
 
   if (setup.hosting.useWebFrameworks) {
-    setup.hosting.source = await input({
+    setup.hosting.source ??= await input({
       message: "What folder would you like to use for your web application's root directory?",
       default: "hosting",
     });
@@ -92,7 +92,7 @@ export async function doSetup(setup: any, config: any, options: Options): Promis
 
     if (discoveredFramework) {
       const name = WebFrameworks[discoveredFramework.framework].name;
-      setup.hosting.useDiscoveredFramework = await confirm({
+      setup.hosting.useDiscoveredFramework ??= await confirm({
         message: `Detected an existing ${name} codebase in ${setup.hosting.source}, should we use this?`,
         default: true,
       });