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
Hi @cenk1cenk2, thanks for opening this issue. Having project-local configuration is part of prettier's philosophy and I wouldn't want to deviate from that.
Prettier intentionally doesn’t support any kind of global configuration. This is to make sure that when a project is copied to another computer, Prettier’s behavior stays the same. Otherwise, Prettier wouldn’t be able to guarantee that everybody in a team gets the same consistent results.
In terms of supporting the flags, I think that's an OK addition. Ideally everyone would be using local config files, but if pretter supports flags, we could support the same parameters.
That would be a great addition for me. I can give it a go this weekend if you don't have enough time. Since I prefer single quotes in every where and sometimes there is no prettier configuration in the workspaces that I work, mostly yml files related to developer operations.
If you accept the other approach, overriding the behaviour from prettier, I can give it a go to that like enabling it with a environmental variable to be sure DEFAULT_CONFIG=~/.prettierrc prettierd ... or something like that.
Hello @fsouza ,
Is it possible to pass configuration options to prettier itself via flags? Or even enabling a global fallback prettierrc creating
.prettierrc
on~
?The text was updated successfully, but these errors were encountered: