chore(deps): update dependency stylelint-config-standard to v24

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
stylelint-config-standard	22.0.0 -> 24.0.0

---

Release Notes

stylelint/stylelint-config-standard

v24.0.0

Compare Source

• Changed: alpha-value-notation to be "number" for opacity property.

v23.0.0

Compare Source

This release adds over a dozen new rules.

If needed, you can extend the config to turn off or lower the severity of any of the new rules.

We recommend using Autoprefixer to automatically prefix your at-rules, properties, selectors and values.

• Removed: stylelint less than 14.0.0 from peer dependencies.
• Changed: updated to [email protected].
• Added: alpha-value-notation rule.
• Added: at-rule-no-vendor-prefix rule.
• Added: color-function-notation rule.
• Added: custom-media-pattern rule.
• Added: custom-property-pattern rule.
• Added: declaration-block-no-redundant-longhand-properties rule.
• Added: font-family-name-quotes rule.
• Added: function-url-quotes rule.
• Added: hue-degree-notation rule.
• Added: keyframes-name-pattern rule.
• Added: max-line-length rule.
• Added: media-feature-name-no-vendor-prefix rule.
• Added: no-empty-first-line rule.
• Added: no-irregular-whitespace rule.
• Added: number-max-precision rule.
• Added: property-no-vendor-prefix rule.
• Added: selector-attribute-quotes rule.
• Added: selector-class-pattern rule.
• Added: selector-id-pattern rule.
• Added: selector-no-vendor-prefix rule.
• Added: shorthand-property-no-redundant-values rule.
• Added: string-quotes rule.
• Added: value-no-vendor-prefix rule.

---

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

[pull-request-quantifier-deprecated]

This PR has 20 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       : +10 -10
Percentile : 8%

Total files changed: 2

Change summary by file extension:
.json : +1 -1
.yaml : +9 -9

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 detetcted.
• 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.