@mjbvz and @jrieken can you take a look at this?

@sandersn There are some eslint failures. You can see them when running yarn eslint (actually the precommit hooks should have reported them...)

I wonder if we should grow the typescript.experimental.aiQuickFix setting, e.g this isn't just quick fixes anymore and also more nuanced. Maybe a new setting like typescript.exprimental.aiCodeActions which value is a complex object would be best, e.g each key would correspond to a feature

Ah, that's right. I completely messed up the setup of vscode's formatter, so I skipped the precommit hook. I'll go back and figure that out so the machine can fix the formatting for me.

Edit: I didn't know about typescript.enable.format, but somehow set it to false in the past. Makes it very hard to format documents with it.

OK, I added a more complex options object. If you just create the top-level object as {}, all the code actions are enabled. Then you can set individual ones to false.

I don't know if this is the usual way to do it, so please let me know if there's a standard I should follow.

I realised that the config still effectively defaulted to true, and that the altered descriptions weren't working.
I fixed that and also created custom descriptions, so please take a look at those for wording.

Linux smoke test case failed:
1) verifies that auto save triggers on shutdown

But I don't see how that could be related to my change.

Merging caused a build failure down the line (when doing the product build...) A revert PR is up (#193810) and this needs to be reopened and looked at again

How can I see the build failure?