Vim-prettier: Why do the defaults differ?

[larister]

Do you want to request a feature or report a bug?

Neither - just ask a question

What is the current/expected behavior?

The Readme.md states the following:

Note: vim-prettier default settings differ from prettier intentionally.

However, there's no reasoning as to why. Is it just personal preference? If so, perhaps it's worth clarifying that in the Readme (happy to do this if you agree).

Additionally/alternatively, it might be good to have a g:prettier#use_prettier_defaults setting rather than having to override them manually.

Apologies if I've missed something here; I did try to check previous issues. Thanks so much for all your work on this, I love it!

What version of vim-prettier are you using - (output of :PrettierVersion) ?

0.2.6

What version of prettier are you using - (output of :PrettierCliVersion) ?

1.11.1

[docwhat]

This will change in v1.0.0 — there is already some changes in this direction in the release/1.x branch.

[masaeedu]

@docwhat Are the settings listed in the README the comprehensive set that differs from default settings?

[docwhat]

I believe so.

_{Sent with GitHawk}

[euoia]

Just bumping this, it took me ages to figure out why the defaults were different. The main problem I had is that the eslint-plugin-prettier module would complain about things that were being fixed by vim-prettier.

I would much prefer for vim-prettier to use the prettier defaults by default. I have pulled in the release/1.x branch, and this seems to fix the issue.