Decide how to format based on package.json

[bcomnes]

💧 Shower thought: What if this plugin decided on which linter to use based on package.json?

Originally I pondered adding a formatter field to package.json, but we don't need that. It should be some kind of dependency for the project using it which essentially offers up consent to autoformatting.

• This would solve our pathing issues
• We could use formatters that follow the same interface by keeping a static list
• Autoformatting would disable automatically an appropriate formatter is not found in the project root package.json.

The goal here is to eliminate busy work enabling and disabling linters when they differ between projects. Has this been a problem for anyone else?

[Flet]

Yeah I've done the dance between standard and semistandard and its a little tiresome... This is a good idea!

How can it be done reliably?

[bcomnes]

Re-implement package.json discovery in python based on project folders (or shell out to JS)? It might get a bit logically harry but I think we can manage it.

No package.json you ask? Why are you developing js without a package.json 😈

But seriously, in that case Leave the keyboard shortcuts/pallet commands active with a command pallet formatter selector maybe?

[Flet]

What would be the indicator in package.json that something is standard or semistandard or doublestandard? :)

[bcomnes]

The indicator would be that it has one of those packages installed and saved to its dependency list.

[bcomnes]

Closing in favor of #35