chore(deps): bump the dart_style group in /packages/worker_bee/worker_bee_builder with 4 updates

[dependabot]

Bumps the dart_style group in /packages/worker_bee/worker_bee_builder with 4 updates: dart_style, code_builder, source_gen and analyzer.

Updates dart_style from 2.3.7 to 3.0.1

Release notes

Sourced from dart_style's releases.

package:dart_style v3.0.1

• Handle trailing commas in for-loop updaters (#1354).
• Format || patterns like fallthrough cases in switch expressions (#1602).
• Handle comments and metadata before variables more gracefully (#1604).
• Ensure comment formatting is idempotent (#1606).
• Better indentation of leading comments on property accesses in binary operator operands (#1611).
• Don't crash on doc comments in local variable declarations (#1621).

package:dart_style v3.0.0

This is a large change. Under the hood, the formatter was almost completely rewritten, with the codebase now containing both the old and new implementations. The old formatter exists to support the older "short" style and the new code implements the new "tall" style.

The formatter uses the language version of the formatted code to determine which style you get. If the language version is 3.6 or lower, the code is formatted with the old style. If 3.7 or later, you get the new tall style. You typically control the language version by setting a min SDK constraint in your package's pubspec.

In addition to the new formatting style, a number of other API and CLI changes are included, some of them breaking:

• Support project-wide page width configuration. By long request, you can now configure your preferred formatting page width on a project-wide basis. When formatting files, the formatter will look in the file's directory and any surrounding directories for an analysis_options.yaml file. If it finds one, it looks for the following YAML:

  formatter:
    page_width: 123

  If it finds a formatter key containing a map with a page_width key whose value is an integer, then that is the page width that the file is formatted using. Since the formatter will walk the surrounding directories until it finds an analysis_options.yaml file, this can be used to globally set the page width for an entire directory, package, or even collection of packages.

• Support overriding the page width for a single file. In code formatted using the new tall style, you can use a special marker comment to control the page width that it's formatted using:

... (truncated)

Changelog

Sourced from dart_style's changelog.

3.0.1

• Handle trailing commas in for-loop updaters (#1354).
• Format || patterns like fallthrough cases in switch expressions (#1602).
• Handle comments and metadata before variables more gracefully (#1604).
• Ensure comment formatting is idempotent (#1606).
• Better indentation of leading comments on property accesses in binary operator operands (#1611).
• Don't crash on doc comments in local variable declarations (#1621).

3.0.0

This is a large change. Under the hood, the formatter was almost completely rewritten, with the codebase now containing both the old and new implementations. The old formatter exists to support the older "short" style and the new code implements the new "tall" style.

The formatter uses the language version of the formatted code to determine which style you get. If the language version is 3.6 or lower, the code is formatted with the old style. If 3.7 or later, you get the new tall style. You typically control the language version by setting a min SDK constraint in your package's pubspec.

In addition to the new formatting style, a number of other API and CLI changes are included, some of them breaking:

• Support project-wide page width configuration. By long request, you can now configure your preferred formatting page width on a project-wide basis. When formatting files, the formatter will look in the file's directory and any surrounding directories for an analysis_options.yaml file. If it finds one, it looks for the following YAML:

  formatter:
    page_width: 123

  If it finds a formatter key containing a map with a page_width key whose value is an integer, then that is the page width that the file is formatted using. Since the formatter will walk the surrounding directories until it finds an analysis_options.yaml file, this can be used to globally set the page width for an entire directory, package, or even collection of packages.

• Support overriding the page width for a single file. In code formatted using the new tall style, you can use a special marker comment to control the page width that it's formatted using:

... (truncated)

Commits

• d76b6ee Bump version number to publish 3.0.1. (#1631)
• 21de99e Add regression test for #1628. (#1629)
• b6e6bfc Update grinder script. (#1627)
• 67ba681 Better debug diagnostics in the solver. (#1624)
• e9bd213 Don't crash on doc comments inside local variable declarations. (#1623)
• 7c4a960 Format || patterns like fallthrough cases in switch expressions. (#1620)
• 47bcc07 Add benchmark and regression test for #1521. (#1619)
• e12c007 Add regression test for #624. (#1618)
• 1198bf7 Handle trailing commas in for-loop updaters. (#1616)
• 04883d6 Better indentation for property access as binary operator operand. (#1615)
• Additional commits viewable in compare view

Updates code_builder from 4.10.0 to 4.10.1

Release notes

Sourced from code_builder's releases.

package:code_builder v4.10.1

• Require Dart ^3.5.0
• Upgrade to dart_style 2.3.7.
• Move to dart-lang/tools monorepo.

Commits

• See full diff in compare view

Updates source_gen from 1.5.0 to 2.0.0

Release notes

Sourced from source_gen's releases.

package:source_gen v2.0.0

• Breaking Change: Change formatOutput function to accept a language version parameter.
• Formatting Change: Generated code will no longer apply any fixes by default (previously it would apply the single cascades statements fix). The new formatter does not support applying fixes.
• Document deduplication behavior for the output of GeneratorForAnnotation.generateForAnnotatedElement.
• Support all the glob quotes.
• Require analyzer: '>=6.9.0 <8.0.0'
• Support the latest package:dart_style
• LibraryBuilder, PartBuilder, and SharedPartBuilder now take an optional writeDescriptions boolean. When set to false, headers and generator descriptions for the files will not be included in the builder output.
• Include //dart format width=80 comments in files generated by a LibraryBuilder or PartBuilder and formatted with the default callback.
• Require Dart 3.6.0

Commits

• 947a0e2 Support latest analyzer and dart_style, prepare v2 release (#736)
• 49a96d8 Bump mind SDK to 3.6.0 stable (#734)
• 9f95ac3 Only add dart format width comment on format (#733)
• b7b0c7d Bump dart-lang/setup-dart in the github-actions group (#732)
• 18c17fc Bump the github-actions group with 2 updates (#731)
• 936fb07 blast_repo fixes (#730)
• eb98c68 Read libraryImports/libraryExports from the defining unit. (#729)
• 2bea904 Read parts with the defining compilation unit (#728)
• da1190d Add dart format width comments (#725)
• 4b4431f Ignore some deprecated analyzer members (#726)
• Additional commits viewable in compare view

Updates analyzer from 6.11.0 to 7.1.0

Commits

• See full diff in compare view

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 show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions