Add reformat tweak

[mosuem]

To be used when dart format had any changes in a stable SDK release.

---

• I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Contribution guidelines:

• See our contributor guide for general expectations for PRs.
• Larger or significant changes should be discussed in an issue before creating a PR.
• Contributions to our repos should follow the Dart style guide and use dart format.
• Most changes should add an entry to the changelog and may need to rev the pubspec package version.
• Changes to packages require corresponding tests.

Note that many Dart repos have a weekly cadence for reviewing PRs - please allow for some latency before initial review feedback.

[github-actions]

PR Health

Package publish validation ✔️

Details

Package	Version	Status
package:dart_flutter_team_lints	2.1.1	already published at pub.dev
package:firehose	0.3.32	already published at pub.dev

Documentation at https://github.com/dart-lang/ecosystem/wiki/Publishing-automation.

License Headers ✔️

Details

// Copyright (c) 2023, the Dart project authors. Please see the AUTHORS file
// for details. All rights reserved. Use of this source code is governed by a
// BSD-style license that can be found in the LICENSE file.

Files
no missing headers

All source files should start with a license header.

Coverage ⚠️

Details

File	Coverage
pkgs/firehose/lib/firehose.dart	💔 Not covered
pkgs/firehose/lib/src/health/health.dart	💔 Not covered

This check for test coverage is informational (issues shown here will not fail the PR).

This check can be disabled by tagging the PR with skip-coverage-check

Breaking changes ⚠️

Details

Package	Change	Current Version	New Version	Needed Version	Looking good?
dart_flutter_team_lints	None	2.1.1	2.1.1	2.1.1	✔️
firehose	Non-Breaking	0.3.32	0.3.32	0.4.0	⚠️

This check can be disabled by tagging the PR with skip-breaking-check

[devoncarew]

I would avoid this path-relative dep if possible.

[mosuem]

I thought that blast_repo not being published means we can relax the principle of reducing the number of imports :) I am also fine with code duplication if that's the lesser evil.

[devoncarew]

It's not wrong - avoiding publishing another package is more important. Perhaps add a line of docs here - # Re-using the repo scanning logic from firehose or similar.

[mosuem]

I am not sure I understand - does this mean you would rather want to copy the code or add the dep with a comment?