fix(deps): bump prettier from 2.5.1 to 2.8.2

[dependabot]

Bumps prettier from 2.5.1 to 2.8.2.

Release notes

Sourced from prettier's releases.

2.8.2

🔗 Changelog

2.8.1

🔗 Changelog

2.8.0

diff

🔗 Release note

2.7.1

🔗 Changelog

2.7.0

diff

🔗 Release note

2.6.2

🔗 Changelog

2.6.1

🔗 Changelog

2.6.0

🔗 Release note

Changelog

Sourced from prettier's changelog.

2.8.2

diff

Don't lowercase link references (#13155 by @​DerekNonGeneric & @​fisker)

<!-- Input -->
We now don't strictly follow the release notes format suggested by [Keep a Changelog].
<!-- Prettier 2.8.1 -->
We now don't strictly follow the release notes format suggested by Keep a Changelog.
<!--
^^^^^^^^^^^^^^^^^^ lowercased
-->
<!-- Prettier 2.8.2 -->
<Same as input>

Preserve self-closing tags (#13691 by @​dcyriller)

{{! Input }}
<div />
<div></div>
<custom-component />
<custom-component></custom-component>
<i />
<i></i>
<Component />
<Component></Component>
{{! Prettier 2.8.1 }}
<div></div>
<div></div>
<custom-component></custom-component>
<custom-component></custom-component>
<i></i>
<i></i>
<Component />
<Component />
{{! Prettier 2.8.2 }}
</tr></table>

... (truncated)

Commits

• ac88438 Release 2.8.2
• aaf9190 Fix comments after directive (#14081)
• 9e09a78 Stop inserting space in LESS property access (#14103)
• 0c5d4f3 Fix removing commas from function arguments in maps (#14089)
• b77d912 ember / glimmer: Preserve self-closing tags (#13691)
• cf36209 Handlebars: Add tests for {{! prettier-ignore}} (#13693)
• f8e1ad8 Add parens to head of ExpressionStatement instead of whole statement (#14077)
• 8034bad Build(deps): Bump json5 from 2.2.0 to 2.2.3 in /scripts/release (#14104)
• 31d4010 Build(deps): Bump json5 from 2.2.1 to 2.2.3 in /website (#14101)
• 41cee06 Do not change case of property name if inside a variable declaration in LESS ...
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by prettier-bot, a new releaser for prettier since your current version.

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Dependabot tried to add @GregoireF and @NicolasV as reviewers to this PR, but received the following error from GitHub:

POST https://api.github.com/repos/wr-projects/cz-changelog-wrprojects/pulls/192/requested_reviewers: 422 - Reviews may only be requested from collaborators. One or more of the users or teams you specified is not a collaborator of the wr-projects/cz-changelog-wrprojects repository. // See: https://docs.github.com/rest/reference/pulls#request-reviewers-for-a-pull-request

[pull-request-quantifier-deprecated]

This PR has 0 quantified lines of changes. In general, a change size of upto 200 lines is ideal for the best PR experience!

---

Quantification details

Label      : No Changes
Size       : +0 -0
Percentile : 0%

Total files changed: 1

Change summary by file extension:
.lock : +0 -0

Change counts above are quantified counts, based on the PullRequestQuantifier customizations.

Why proper sizing of changes matters

Optimal pull request sizes drive a better predictable PR flow as they strike a
balance between between PR complexity and PR review overhead. PRs within the
optimal size (typical small, or medium sized PRs) mean:

• Fast and predictable releases to production:
  • Optimal size changes are more likely to be reviewed faster with fewer
    iterations.
  • Similarity in low PR complexity drives similar review times.
• Review quality is likely higher as complexity is lower:
  • Bugs are more likely to be detected.
  • Code inconsistencies are more likely to be detected.
• Knowledge sharing is improved within the participants:
  • Small portions can be assimilated better.
• Better engineering practices are exercised:
  • Solving big problems by dividing them in well contained, smaller problems.
  • Exercising separation of concerns within the code changes.

What can I do to optimize my changes

• Use the PullRequestQuantifier to quantify your PR accurately
  • Create a context profile for your repo using the context generator
  • Exclude files that are not necessary to be reviewed or do not increase the review complexity. Example: Autogenerated code, docs, project IDE setting files, binaries, etc. Check out the Excluded section from your prquantifier.yaml context profile.
  • Understand your typical change complexity, drive towards the desired complexity by adjusting the label mapping in your prquantifier.yaml context profile.
  • Only use the labels that matter to you, see context specification to customize your prquantifier.yaml context profile.
• Change your engineering behaviors
  • For PRs that fall outside of the desired spectrum, review the details and check if:
    • Your PR could be split in smaller, self-contained PRs instead
    • Your PR only solves one particular issue. (For example, don't refactor and code new features in the same PR).

How to interpret the change counts in git diff output

• One line was added: +1 -0
• One line was deleted: +0 -1
• One line was modified: +1 -1 (git diff doesn't know about modified, it will
  interpret that line like one addition plus one deletion)
• Change percentiles: Change characteristics (addition, deletion, modification)
  of this PR in relation to all other PRs within the repository.

---

Was this comment helpful? 👍  :ok_hand:  :thumbsdown: (Email)
Customize PullRequestQuantifier for this repository.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[dependabot]

Superseded by #193.