Added voice command to migrate Cursorless snippet to community format

[AndreasArvidsson]

2 fields in the Cursorless snippets are not available in the community format

1. scopeTypes. To my knowledge the only use case is omitting the function keyword when in a javascript class
2. excludeDescendantScopeTypes: Used in conjunction with scopeTypes to include the function keyword when in a function inside a class.

scopeTypes and excludeDescendantScopeTypes I'm not to sure we want to add to community. First of all they have a single use case and needing two separate fields just to describe this behavior fields a bit verbose.
As well community doesn't have support for sending multiple snippets.

I'm planning this as a follow up.

Reference

cursorless/packages/common/src/types/snippet.types.ts

Lines 4 to 24 in 57acd6c

	export interface SnippetScope {
	/**
	* VSCode language ids where this snippet definition should be active
	*/
	langIds?: string[];
	/**
	* Cursorless scopes in which this snippet is active. Allows, for example, to
	* have different snippets to define a function if you're in a class or at
	* global scope.
	*/
	scopeTypes?: SimpleScopeTypeType[];
	/**
	* Exclude regions of {@link scopeTypes} that are descendants of these scope
	* types. For example, if you have a snippet that should be active in a class
	* but not in a function within the class, you can specify
	* `scopeTypes: ["class"], excludeDescendantScopeTypes: ["namedFunction"]`.
	*/
	excludeDescendantScopeTypes?: SimpleScopeTypeType[];
	}

Fixes #2355

Checklist

• I have added tests
• I have updated the docs and cheatsheet
• [/] I have not broken the cheatsheet

[phillco]

CURSORLESS_SNIPPETS_SUFFIX?

[phillco]

Checking for file existence separately from opening the file is generally racy, best to just do this:

Suggested change

	const file = await fs.open(filePath, "w");
	const file = await fs.open(filePath, "wx");

'wx': Like 'w' but fails if the path exists.

Then catch and put your conflict filename behavior in the catch block.

[pokey]

What does this tool do with the scopeTypes and excludeDescendantScopeTypes fields if you're using them?

[AndreasArvidsson]

What does this tool do with the scopeTypes and excludeDescendantScopeTypes fields if you're using them?

Discards them. These fields are not really used that much (There is only one use case as far as I know). And since we haven't decided on the format we are going to use in the future I want to avoid a community to community migration script if we decide to use something else.

[pokey]

I would bail if you encounter them. Silently dropping data is not good ux

[AndreasArvidsson]

You mean bail on the entire migration or just on that snippet?

[pokey]

Maybe just that snippet? I don't feel strongly, as long as we raise a flag rather than silently losing data

[AndreasArvidsson]

Totally agree. Here is the follow up.
#2789