ux: unexpected behavior after selecting No after being asked Always configure projects upon opening?

[ymleung314]

When I opened a directory with a CMake project, I was asked Always configure projects upon opening?, which I clicked No. Then, the workspace setting cmake.configureOnOpen is set to true automatically. However, I don't see why, when I literally just said "don't configure projects upon opening", the currently opened workspace should be configured on open.

[gcampbell-msft]

Are you able to reliably reproduce this? If so, this is definitely a bug, and we'd like to have a GitHub issue created for this to track and investigate. Please let us know so that we can investigate. Thanks!

[gcampbell-msft]

Thanks for the feedback. We've gotten lots of feedback about those pop-ups, both about the wording and the presence of them at all, so we are in the midst of investigating simply changing to a default of true for cmake.configureOnOpen. Then, users can modify the setting themselves if desired.

What are your thoughts on this?

[ymleung314]

I wonder if you guys have already changed that as I am no longer seeing that prompt, straight up configuration on open every time. I would say, for an existing user, that could feel surprising. That also means trusting the workspace leads to immediate configuration, not something everyone always wants.

[gcampbell-msft]

That's good feedback. However, to ease some of those concerns, we would only be changing the default, so anyone who has already answered "yes" or "no" to the configureOnOpen UI, this would not affect.

The workspace trust is a good callout though.

[ymleung314]

So those prompts will never pop up?

[gcampbell-msft]

Correct