Bump the all_dependencies group in /packages/leancode_lint with 4 updates

[dependabot]

Bumps the all_dependencies group in /packages/leancode_lint with 4 updates: analysis_server_plugin, analyzer_plugin, analyzer and analyzer_testing.

Updates analysis_server_plugin from 0.3.8 to 0.3.13

Commits

• See full diff in compare view

Updates analyzer_plugin from 0.14.2 to 0.14.7

Commits

• See full diff in compare view

Updates analyzer from 10.0.2 to 12.0.0

Commits

• See full diff in compare view

Updates analyzer_testing from 0.1.10 to 0.2.4

Changelog

Sourced from analyzer_testing's changelog.

3.12.0

Released on: Unreleased

Language

Private named parameters

Dart now supports private named parameters. Before 3.12, it was an error to have a named parameter that starts with an underscore:

class Point {
  final int _x, _y;
  // Compile error in Dart 3.11.
  Point({required this._x, required this._y});
}

That means that when you wanted to initialize a private field from a named parameter, you had to write an explicit initializer list:

class Point {
  final int _x, _y;
  Point({required int x, required int y})
    : x = _x,
      y = _y;
}

All the initializer list is doing is scraping off the _. In Dart 3.12, the language will do that for you. Now you can write:

class Point {
  final int _x, _y; // Private fields.
  Point({required this._x, required this._y});
}

It behaves exactly like the previous example. The initialized fields are private, but the argument names written at the call site are public:

main() {
  print(Point(x: 1, y: 2));
}
</tr></table> 

... (truncated)

Commits

• See full diff in compare view

Updates analyzer from 10.0.2 to 12.0.0

Commits

• See full diff in compare view

Updates analyzer_plugin from 0.14.2 to 0.14.7

Commits

• See full diff in compare view

Updates analyzer_testing from 0.1.10 to 0.2.4

Changelog

Sourced from analyzer_testing's changelog.

3.12.0

Released on: Unreleased

Language

Private named parameters

Dart now supports private named parameters. Before 3.12, it was an error to have a named parameter that starts with an underscore:

class Point {
  final int _x, _y;
  // Compile error in Dart 3.11.
  Point({required this._x, required this._y});
}

That means that when you wanted to initialize a private field from a named parameter, you had to write an explicit initializer list:

class Point {
  final int _x, _y;
  Point({required int x, required int y})
    : x = _x,
      y = _y;
}

All the initializer list is doing is scraping off the _. In Dart 3.12, the language will do that for you. Now you can write:

class Point {
  final int _x, _y; // Private fields.
  Point({required this._x, required this._y});
}

It behaves exactly like the previous example. The initialized fields are private, but the argument names written at the call site are public:

main() {
  print(Point(x: 1, y: 2));
}
</tr></table> 

... (truncated)

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 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