config file doesn't work at the way other libraries do #2691
Description
First, It's very exciting that config file support is out.
However, after a few tries, I find its usage is a bit ambiguous.
For example, I define a .prettierrc like the follow:
{
"printWidth": 120,
"tabWidth": 2,
"singleQuote": true,
"semi": false,
"trailingComma": "all",
"overrides": [
{
"files": "src/**/*.ts",
"options": {
"parser": "typescript",
"tabWidth": 4
}
},
{
"files": "./**/*.js",
"options": {
"parser": "babylon",
"singleQuote": false
}
},
{
"files": "src/**/*.{scss,css}",
"options": {
"parser": "postcss",
"singleQuote": false,
"semi": true
}
},
{
"files": "./**/*.json",
"options": {
"parser": "json"
}
},
{
"files": ".prettierrc",
"options": {
"parser": "json"
}
}
]
}Since I specify the files in overrides, prettier should do the right job with prettier --write or prettier --list-difference.
However, prettier doesn't work that way now. If I run the command above, prettier will only output the help message and exit. Apparently, prettier is waiting for source input. But it doesn't make sense to specify input again.
There is a dirty workaround prettier --write ./**/**.{ts,js,json,scss,css}. But it lose the ability to prettier various specify path.