chore(deps): update dependency prettier to v1.11.1 - autoclosed

[renovate]

This Pull Request updates dependency prettier from v1.7.4 to v1.11.1

Note: This PR was created on a configured schedule ("every weekend" in timezone Europe/Paris) and will not receive updates outside those times.

Release Notes

v1.8.0

link

• Release Notes

---

v1.8.1

link

• Force JSON to no trailing comma in multiparser (#​3182 by azz)
• Don't add trailing commas in JSXAttribute for arrow functions (#​3181 by duailibe)
• Markdown: Allow more cases that _-style emphasis is available (#​3186 by ikatyang)
• Markdown: Handle additional spaces before code (#​3180 by ikatyang)
• Markdown: Do not break on unbreakable place (#​3177 by ikatyang)
• Markdown: Do not break before special prefix (#​3172 by ikatyang)

---

v1.8.2

link

• Markdown: Don't break on links (#​3204 by ikatyang)
• Markdown: Add --no-prose-wrap option (#​3199 by ikatyang)
• TypeScript: Parenthesis around TSAsExpression inside TSAbstractClassDeclaration (#​3191 by duailibe)
• JSON: Print JSON top comments as leading comments of root node (#​3187 by duailibe)

---

v1.9.0

link

• Release Notes

---

v1.9.1

link

• Fixed a bug of comments with JSX fragments being duplicated in output (#​3398 by duailibe)
• Fixed a bug that Prettier would fail when using tabs (#​3401 by ikatyang)
• Fixed a regression that removed trailing commas when printing JS code blocks in Markdown (#​3405 by azz)
• Fixed a bug when using glob **/* which would try to format directories (#​3411 by duailibe)
• Fixed a bug when .editorconfig had max_line_length = "off" (#​3412 by duailibe)

---

v1.9.2

link

• Fixed trailing comma not being printed in function calls if the last arg was an arrow (#​3428 by duailibe)
• Ignore whitespace after the /** in docblocks (#​3430 by duailibe)
• Fixed a bug where get and set class properties arrows would print an unnecessary semicolon with --no-semi (#​3434 by duailibe)
• Fixed a bug for missing .editorconfig files (#​3439 by josephfrazier)
• Fix comments being moved in class methods and object properties with the babylon parser (#​3441 by duailibe)
• Better printing of member chains with a TSNonNullExpression (! character) (#​3442 by duailibe)
• Fix missing commas in object properties when a pretter-ignore comment is present (#​3448 by duailibe)
• Fix printing union types inside a function param type (#​3446 by duailibe)
• Fix closing parens on multi-line intersection/union type (#​3436 by josephfrazier)
• Don't break single argument destructuring arguments (for arrays and with simple default values) (#​3443 by duailibe)

---

v1.10.0

link

• Release Notes

---

v1.10.1

link

• Fixed an issue where the CLI fails to resolve a file.

---

v1.10.2

link

• Fixed an issue printing .vue files with self-closing tags. (#​3705 by duailibe)

---

v1.11.0

• Release Notes

---

v1.11.1

link

• 1.11.0 was incorrectly shipped with the wrong version of the TypeScript parser, which broke conditional types. This release fixes it.
• Fixed an issue relating to deprecated parsers (#​4072)

---

Commits

v1.11.0

• 0109333 Mention webstorm built-in support on homepage (#​4037)
• a066812 Do not require plugins to set 'since' field (#​4038)
• 5153b15 Respect EditorConfig when --config is passed (#​3992)
• 29ef3f0 Enhancing pre-commit bash script documentation. (#​3638)
• c1107a8 feat(markdown): respect tabWidth for list items (#​3990)
• 9ee113c webpack/webpack now uses Prettier (#​4039)
• 7919603 Webpack -> webpack
• ca81bef fix(markdown): list prefix: no unnecessary trailing spaces (#​4042)
• b6c2789 fix(markdown): list prefix alignment: count spaces from correct place (#​4041)
• 65b988a feat: ignore non standard IE filter values (#​4028)
• efd5bde Fix(typescript) non-null identifier same line in chain (#​4052)
• 4ddf1a6 fix: don't lowercase nesting selector (#​4048)
• b1b504f 1.11 Release Notes and Changelog (#​4035)

v1.11.1

• 82492de Bump version to 1.11.0
• 51202f4 Format 2-26 blog post with prettier
• 74a132c Bump own prettier dependency version to 1.11.0 (#​4058)
• 23f032f Fix @​orta's link (#​4060)
• d05a29d Allow plugins to override default options (#​3991)
• 0ce4ce3 fix(api): no regression for deprecated parser (#​4072)
• 2897c95 Try to clarify when to use the issue template (#​4059)
• 0f1757a Bump version to 1.11.1

---

This PR has been generated by Renovate Bot.

[algobot]

Deploy preview for algolia-instantsearch ready!

Built with commit f74c3c8

https://deploy-preview-2556--algolia-instantsearch.netlify.com

[bobylito]

Even though it's easy to fix, it's still annoying to have a new commit to change again the whole codebase...

[vvo]

Even though it's easy to fix, it's still annoying to have a new commit to change again the whole codebase...

You can also ignore prettier upgrades if that's a struggle.

@rarkins any plan in making prettier upgrade easier by running --autofix for example? Thanks

[vvo]

There's also https://stylejs.io/

[rarkins]

@vvo there's an open feature request for post-upgrade tasks: renovatebot/renovate#838

Naturally this would include eslint --fix too.

I'm a little hesitant on this one, as I can't see any way to avoid needing to git clone the entire repo, like is done on a CI system. I've been pretty happy to avoid having full copy of repos on Renovate servers for multiple reasons (disk, my security, your security, etc) but it also sounds like a killer feature.

[bobylito]

The problem is not the upgrade in itself, it's the fact that we will have to add a new commit only for formatting the code. This commit is noise and it makes looking into the history more complex (when using git blames)

[rarkins]

@bobylito is using a squash merge on these types of PRs out of the question? Then it would become a single commit in your master history (I mean in the current case where a human has to intervene)

[Haroenv]

The point of @bobylito is simply that the history is "clouded" by changes made by the prettier, rather than real changes, if it's squashed or not does not really make a difference. I don't think there's anything we can do about that.

[rarkins]

@Haroenv OK I see what you mean. Yes, it's a bit of a pain if your git blame starts getting dominated by whomever applies the prettier updates. It was meant to settle down post-v1 but I see it makes quite a lot of impact sometimes.

[rarkins]

Broken due to #2398