Skip to content

feat: pubworkspace this repository - #103

Merged
jtmcdole merged 3 commits into
mainfrom
workspace
May 1, 2026
Merged

jtmcdole merged 3 commits into
mainfrom
workspace

Conversation

@jtmcdole

@jtmcdole jtmcdole commented May 1, 2026

Copy link
Copy Markdown
Member

One place to run "flutter pub get".

Brings up the lower end dart to ^3.10.8, upgrades lints and packages.

Pre-launch Checklist

  • I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
  • I read the [Tree Hygiene] wiki page, which explains my responsibilities.
  • I read the [Flutter Style Guide] recently, and have followed its advice.
  • I signed the [CLA].
  • I listed at least one issue that this PR fixes in the description above.
  • I updated/added relevant documentation (doc comments with ///).
  • I added new tests to check the change I am making, or this PR is [test-exempt].
  • All existing and new tests are passing.

One place to run "flutter pub get".

Brings up the lower end dart to ^3.10.8, upgrades lints and packages.
@jtmcdole
jtmcdole requested a review from reidbaker May 1, 2026 17:36

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request migrates the repository to a Dart workspace, incorporating the tool/generator and tool/dart_skills_lint packages. It includes significant dependency updates and an SDK version bump. The review feedback identifies a critical mismatch between the Dart SDK version required by the pubspec.lock (3.11.0) and the pubspec.yaml files (3.10.8). Furthermore, the lock file contains inconsistencies regarding dependency types and missing workspace members, suggesting it needs to be regenerated at the workspace root.

Comment thread pubspec.lock Outdated
Comment thread pubspec.lock Outdated
Comment thread pubspec.yaml
Comment thread tool/dart_skills_lint/pubspec.yaml
Comment thread tool/generator/pubspec.yaml
@reidbaker

reidbaker commented May 1, 2026 •

Copy link
Copy Markdown
Contributor

Lgtm from @jwren in chat to make skills a workspace.

@jtmcdole

jtmcdole commented May 1, 2026

Copy link
Copy Markdown
Member Author

/gemini review

@jtmcdole
jtmcdole merged commit d03dba1 into main May 1, 2026
11 checks passed

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request configures a Dart workspace and applies extensive formatting updates across the dart_skills_lint package and its tests. The review feedback identifies a few missed opportunities in entry_point.dart to apply consistent multi-line formatting to command-line parser options and flags, which would improve overall readability.

abbr: 's',
help: 'Path to an individual skill directory to validate. Can be specified multiple times.',
)
..addOption(_ignoreFileOption, help: 'Path to a JSON file listing lints to ignore for the run.')

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The addOption call for _ignoreFileOption is missing the consistent multi-line formatting applied to other parser configuration calls in this block, which reduces readability.

Suggested change
..addOption(_ignoreFileOption, help: 'Path to a JSON file listing lints to ignore for the run.')
..addOption(
_ignoreFileOption,
help: 'Path to a JSON file listing lints to ignore for the run.',
)

Comment on lines 118 to 119
..addFlag(_fixFlag, negatable: false, help: 'Preview fixes for failing lints (dry run).')
..addFlag(_fixApplyFlag, negatable: false, help: 'Apply fixes for failing lints.')

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The addFlag calls for _fixFlag and _fixApplyFlag are missing the consistent multi-line formatting applied to other parser configuration calls in this block, which reduces readability.

Suggested change
..addFlag(_fixFlag, negatable: false, help: 'Preview fixes for failing lints (dry run).')
..addFlag(_fixApplyFlag, negatable: false, help: 'Apply fixes for failing lints.')
..addFlag(
_fixFlag,
negatable: false,
help: 'Preview fixes for failing lints (dry run).',
)
..addFlag(
_fixApplyFlag,
negatable: false,
help: 'Apply fixes for failing lints.',
)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants