Tom McKearney

Hey @jesperbjensen, you think we should have a dictionary mapping an extension regex to command path to search like this? ```cs // TODO: better name private static readonly IDictionary _specificExtensionCommandMap...

I just realized today that `prettier-eslint` works on strings, which is very useful to us. `prettier-tslint`, however, only works on files, which is much less useful (we want to modify...

@jesperbjensen @madskristensen - should we also be installing our own copy of `prettier-eslint` or just support a local copy of that?

All, I have a functioning version that runs prettier-eslint if it's present. Was going to add it as part of the additional extension support I'm adding too. Just wanted to...

I was just thinking the same thing. Prettier supports lots of formats like: `JavaScript · Flow · TypeScript · CSS · SCSS · Less · JSX · Vue · GraphQL...

@madskristensen @jesperbjensen What do you think? Rename + Support all these formats? Maybe have a list of checkboxes on the options page w/ JS + TS checked by default?

Should I just fork this and do that?

OK, we'll just keep the name the same then? I figured, we could add more options with the list of extensions in the OptionsPage for each extension type as well

So, it seems that there are only built-in definitions of the following content types: "TypeScript", "JavaScript", "css", "LESS" and "SCSS" out of this list from the prettier site: JavaScript ·...

Your version numbers don't make sense. Maybe you are talking about VS Code? If so, this extension doesn't run in VS Code. Additionally, I think it only formats JavaScript and...