Add multiple file creation with curly brackets pattern

[kuroidoruido]

Sometimes we need to create some files with little variations (same filename but with different extensions, same file in different directory, etc.). So I add the ability to specify these variation with curly brackets (like it can be done in bash for example).

Examples:

• typing foo.{ts,css,spec.ts} will create files: foo.ts, foo.css and foo.spec.ts
• typing {foo,bar}/foo.ts will create files: foo/foo.ts and bar/foo.ts
• typing {foo,bar}/foo.{ts,css,spec.ts} will create files: foo/foo.ts,foo/foo.css,foo/foo.spec.ts,bar/foo.ts,bar/foo.css and bar/foo.spec.ts

To test this, you can create a new file and type a file name with a pattern like one of the examples above

[kuroidoruido]

@microsoft-github-policy-service agree

[kuroidoruido]

@microsoft-github-policy-service agree

[kuroidoruido]

@microsoft-github-policy-service agree

[kuroidoruido]

@microsoft-github-policy-service agree

[lramos15]

This is very neat! Sorry about the angry bot. It makes me wonder if the logic should be expanded even further to support some of the filename expansion like in https://www.npmjs.com/package/brace-expansion

[ArturoDent]

Would these associated changes be available for extension authors? There are lots of extensions that create multiple-file templates for different situations.

[lramos15]

Would these associated changes be available for extension authors? There are lots of extensions that create multiple-file templates for different situations.

I think the answer to that at least in the near future is no. We are not even sure if we should take this in or leave it up to an extension. An extension can currently do this using the vscode filesystem APIs. The main reason it is being considered is because right now is that if you make a file test/foo.js it will create the folder and the file so we already have a little bit of power user file creation in the product.

[miguelsolorio]

Just to add some comments to the discussion, I do think it would be worth starting with very basic use cases since this is still considered a "niche" feature (similar to creating files in new folders i.e. foo/bar.js). So going with something like foo.{ts,css,spec.ts} or foo.ts,bar.css,spec.ts seems like a good starting point.

I'd avoid getting too complex in supporting every expansion known as the cost might outweigh the benefit.

[vivodi]

Is this still relevant?