search

dgiot / iotStudio

dgiotεΉ³ε°θ‘ŒδΈšεΊ”η”¨ζ‰©ε±•ζ’δ»Ά dgiot for application plugin
https://dgiot-dashboard.vercel.app/
Mozilla Public License 2.0
283 stars 102 forks source link

chore(deps-dev): bump prettier from 2.4.1 to 2.8.0 #638

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 2 years ago

Bumps prettier from 2.4.1 to 2.8.0.

Release notes

Sourced from prettier's releases.

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

2.5.1

πŸ”— Changelog

2.5.0

diff

πŸ”— Release note

Changelog

Sourced from prettier's changelog.

2.8.0

diff

πŸ”— Release Notes

2.7.1

diff

Keep useful empty lines in description (#13013 by @​chimurai)

# Input
"""
First line

Second Line
"""
type Person {
name: String
}


Prettier 2.7.0


"""
First line
Second Line
"""
type Person {
name: String
}


Prettier 2.7.1


"""
First line


Second Line
"""
type Person {
name: String
}

2.7.0

diff

πŸ”— Release Notes

... (truncated)

Commits
Maintainer changes

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


Dependabot compatibility score

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)
pull-checklist[bot] commented 2 years ago

Example Check Group #2 (Click here to edit)

vercel[bot] commented 2 years ago

The latest updates on your projects. Learn more about Vercel for Git β†—οΈŽ

Name Status Preview Updated
dgiot-dashboard ❌ Failed (Inspect) Nov 28, 2022 at 5:14AM (UTC)
pull-request-quantifier-deprecated[bot] commented 2 years ago

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

Quantification details

``` Label : Extra Small Size : +1 -1 Percentile : 0.8% Total files changed: 1 Change summary by file extension: .json : +1 -1 ``` > Change counts above are quantified counts, based on the [PullRequestQuantifier customizations](https://github.com/microsoft/PullRequestQuantifier/blob/main/docs/prquantifier-yaml.md).

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](https://github.com/microsoft/PullRequestQuantifier/releases) - 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](./docs/prquantifier-yaml.md) 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? :thumbsup:  :ok_hand:  :thumbsdown: (Email) Customize PullRequestQuantifier for this repository.

dependabot[bot] commented 1 year ago

Superseded by #642.