I think we can add an _available in v1.9.0+_ note just like https://prettier.io/docs/en/options.html#prose-wrap, so that we don't have to uncomment new feature every time and it's clearer which version is available for it.

This doesn't look the same as the current behaviour. We want an empty config file to be different than no config file. How this works with .editorconfig... I don't know. Editors want to support formatting only if a config file is found, so supporting EditorConfig might break that functionality.

This doesn't look the same as the current behaviour.

According to @robwise in #2760 (comment), the current behavior treats missing/empty config files equivalently. I wanted to be sure, so here's a script you can run against a clean build of cbed0f4 to try it out:

tmpdir=`mktemp -d`
tmpfile=$tmpdir/file.js
tmprc=$tmpdir/.prettierrc

echo -n > $tmpfile

echo "With no .prettierrc"
node -p "require('./').resolveConfig.sync('$tmpfile')"
echo

echo "With empty .prettierrc"
echo -n > $tmprc
node -p "require('./').resolveConfig.sync('$tmpfile')"
echo

rm -rf $tmpdir

On my machine, this prints:

With no .prettierrc
null

With empty .prettierrc
null

Because of this, I'd like to fix this missing/empty distinction in a separate PR, since it's pre-existing and (somewhat?) unrelated (see #2760 (comment))

How this works with .editorconfig... I don't know. Editors want to support formatting only if a config file is found, so supporting EditorConfig might break that functionality.

Hmm, I guess the use-case here is:

• The user has a prettier integration in their editor
• The integration is configured to format-on-save if a prettier configuration exists
• The user is working on a project that has a .editorconfig
• But the project's style guide is incompatible with prettier's formatting

Yeah, I could see how that might get tricky. I'm going to have to give it some more thought.

Yeah, I could see how that might get tricky. I'm going to have to give it some more thought.

Ok, so one way to fix this is to make it so that resolveConfigFile() (and its CLI counterpart --find-config-path) return paths to empty .prettierrc files (it doesn't currently). Once that's the case, the editor integration can use it to determine whether an empty .prettierrc exists, even if resolveConfig returns an object derived from .editorconfig.

Using resolveConfigFile(path) != null could be a solution.
I've not seen this function exposed for now, seems to be cli only.

Ok, so one way to fix this is to make it so that resolveConfigFile() (and its CLI counterpart --find-config-path) return paths to empty .prettierrc files (it doesn't currently).

Hmm, it looks like cosmiconfig intentionally ignores empty files: cosmiconfig/cosmiconfig@1adf5c2

However, a .prettierrc file containing just a space or a newline is still found, so that could be the suggested workaround instead of this from #2760 (comment):