Add flag to exit with error instead of asking for interaction

[Rexios80]

Fixes #710

[vercel]

@Rexios80 is attempting to deploy a commit to the FlutterTools Team on Vercel.

A member of the Team first needs to authorize it.

[leoafarias]

@Rexios80 Shouldn't this return a selection or default selection instead of just exiting? Also, we have added an isCI flag. Would it be the same type of behavior to essentially skip selections in this case or select the default, and if no default is set, then exit?

[Rexios80]

The main user input I have issue with is the confirmation to install. The default value for that one is true which is not what I want. It also exits with a success exit code if you say no which is bad since it hides the issue from my tool. As for the selections, I don't see a way to do that without user interaction. The two selections I see (the one for selecting a flutter version and the one for fixing "invalid" flutter versions) both cannot be handled with a default. I mostly added the exit to the select call for consistency with the confirm call, so maybe we can remove that change?

The isCI flag looks promising, but this tool isn't only meant for use in CI so that seems a little weird.

[Rexios80]

I think I misread that you wanted to use the isCI flag for this. Yes this PR should be replicating the same behavior that we would expect in CI.

[leoafarias]

@Rexios80 can I close this in favor of #713?

[Rexios80]

What do you mean "in favor of"? They're two completely separate PRs.

[leoafarias]

The force flag also skips interaction. Which command do you need this no interaction for?

[Rexios80]

Theoretically it could be any command that asks for interaction, but the biggest issue is when fvm asks to install a flutter version with fvm flutter ...

[Rexios80]

@leoafarias What do we need to get this functionality in?

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
fvm	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	May 29, 2024 1:05pm

[leoafarias]

@Rexios80 can you just update the docs on the website to document this flag?

[Rexios80]

@leoafarias Before I do that are we sure we like the flag name "--no-interact"? I didn't put much thought into it and I don't want us to be stuck with something we don't like forever.

[Rexios80]

Maybe "--no-input" would be better? Or even something like "--fvm-no-input" to guarantee it can't conflict with any dart/flutter flags?

[Rexios80]

@leoafarias Please review this when you get a chance