Split confirmWriteProjectFile out of askWriteProjectFile #8648
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.
Doing some refactor to make split prompt and file write actuation easier.
config.writeProjectFile
method. Audited all use cases of it and update surrounding logs to avoid duplications.confirmWriteProjectFile
out ofaskWriteProjectFile
.It's very common in
doSetup
to useaskWriteProjectFile
.After the refactor, we can make
askQuestions
callsconfirmWriteProjectFile
and saves the response.actuate
callsaskWriteProjectFile
.From Empty Folder
Re-running init again
It's arguably better than the existing behavior, which ask for confirmation even if there is no change in Firestore / storage rules.
[Existing] Re-running init