Enable analysis for the tool directory (#3853)

Since the tooling doesn't live in packages/, we're not currently analyzing it. This enables analysis so that we won't have analyzer issues creeping in over time.

To minimize complexity, this just adds it directly to the Cirrus configuration rather than building knowledge of the tool directory into the tool itself.
This commit is contained in:
stuartmorgan
2021-05-07 12:40:28 -04:00
committed by GitHub
parent a0ca28bac6
commit 53c8d479d4
2 changed files with 4 additions and 4 deletions

View File

@ -101,13 +101,13 @@ class DriveExamplesCommand extends PluginCommand {
fileSystem.directory(p.join(example.path, 'integration_test'));
if (await integrationTests.exists()) {
await for (final FileSystemEntity integration_test
await for (final FileSystemEntity integrationTest
in integrationTests.list()) {
if (!integration_test.basename.endsWith('_test.dart')) {
if (!integrationTest.basename.endsWith('_test.dart')) {
continue;
}
targetPaths
.add(p.relative(integration_test.path, from: example.path));
.add(p.relative(integrationTest.path, from: example.path));
}
}

View File

@ -187,7 +187,7 @@ class VersionCheckCommand extends PluginCommand {
// Skip validation for the special NEXT version that's used to accumulate
// changes that don't warrant publishing on their own.
bool hasNextSection = versionString == 'NEXT';
final bool hasNextSection = versionString == 'NEXT';
if (hasNextSection) {
print('Found NEXT; validating next version in the CHANGELOG.');
// Ensure that the version in pubspec hasn't changed without updating