Feat: Wildcards for files association

[wladimirgrf]

This Pull Request introduces a new feature, wildcards for file customization.

Solving this issue: Allow wildcards in files association #93

Example:

config	workspace

[zm-cttae]

Suggested change

	const newExtension = file.replace('*.','');
	const newExtension = file.substring(2);

[miguelsolorio]

@wladimirgrf This is working lovely! One minor question, should we also support ".service.ts": "angular" without the *, to ensure it works multiple ways?

[wladimirgrf]

@wladimirgrf This is working lovely! One minor question, should we also support ".service.ts": "angular" without the *, to ensure it works multiple ways?

@miguelsolorio No, we need to have a character, in this case *, to identify that we should consider the value as an extension and not a file type.

If we only consider the .. We will have problems with customizing files like .nvmrc, .env, .eslintrc.js, any file that starts with ..

Because for cases like *.module.ts I create it as "fileExtensions" and not as "fileNames".

[miguelsolorio]

Ah, that makes sense! In that case let's merge this in. Thanks again! 🍻