You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is something I don鈥檛 want to do because it encourages using dprint without the default configuration, which is not a great experience, and it complicates all the implementations of editor plugins.
It sounds like implementing dprint/dprint#351 should meet your needs?
rivy
changed the title
馃檹 [feat/req] Allow specification of configuration file from VSCode config
馃檹馃徎 [feat/req] Allow specification of configuration file from VSCode config
Apr 16, 2021
It sounds like implementing dprint/dprint#351 should meet your needs?
Yes, that would fix it for me. I just wasn't sure which of the two (if either) would be more palatable to you, or, if other devs might have a different naming scheme in mind.
It would be great to be able to specify a non-default configuration file to be used by the
dprint
formatter for a given workspace.The text was updated successfully, but these errors were encountered: