This should be controlled by a setting for sure.

Here are the outcomes I can see with this feature:

• A user refactors some code, likes the AI generated name and decides to use it.
• A user refactors some code and sees the AI generated name, but they want to make a slight tweak to the name.
• A user reactors some code and doesn't want to use the AI generated names at all.
  • Perhaps the user is consistently getting bad suggestions for the particular thing they are trying to do.
  • Perhaps seeing pre-generated names like newLocal or newFunction is a part of their proofing workflow (with eyeballs, linters, git hooks, or other code analysis tools).
  • The user is against using AI for some other reason

I think TypeScript should try to infer name using common naming conventions at least (such as use... or get...), just like vscode-postfix-ts extension does:

From my experience it covers ~20% of code and can be useful if AI suggestions are slow, unavailable or a user doesn't want to use the AI generated names at all.

Why not instead expose this through an API? So it's not tied to a single technology. It would allow valuable customization to make sure the name conforms to project guidelines, or takes into account various patterns from a given framework. In some cases even allow the name to be inferred statically by the content without AI.

rust-analyzer has a suggest_name utility: https://github.com/rust-lang/rust-analyzer/blob/426d2842c1f0e5cc5e34bb37c7ac3ee0945f9746/crates/ide-assists/src/utils/suggest_name.rs

@DanielRosenwasser - is this the newly added behavior?

Marking this as an exploration. We'll create test items for the individual features that came out of it