-
Notifications
You must be signed in to change notification settings - Fork 247
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(aft): Better handling of pre-release Dart SDK usage #3569
Conversation
57f7e09
to
07b244e
Compare
// The problem of packages setting incorrect constraints, for example setting | ||
// `^3.0.5` when the current repo constraint is `^3.0.0` and we're running | ||
// `aft` with `3.0.1` is a different issue handled by the constraints commands. | ||
(pkg) => pkg.compatibleWithCurrentSdk, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should we print the packages that are ignored as a result? In the future should someone change to a incompatible Dart SDK for whatever reason, perhaps it would be good to notify it's being ignored in bootstrap should some confusion result.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Done 👍
@override | ||
List<Object?> get props => [name]; | ||
|
||
@override | ||
String get runtimeTypeName => 'PackageInfo'; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
General programming approach question - why do we combine multiple classes into the same file? As someone unfamiliar with your aft code it's a bit confusing to have these large files to scroll through and also not being able to search by classes by file name that match the class contained.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added some non blocking comments.
9cf0524
to
32db8b8
Compare
206b2fb
to
50b8e21
Compare
The base branch was changed.
Some packages in the repo (for example, the `actions` pkg) set a pre-release Dart SDK constraint so that preview features of Dart can be leveraged. This updates `aft` so that: 1) `bootstrap` skips packages which set this constraint if the current Dart SDK doesn't support it; and 2) Ignores preview constraints in the constraints checker, since these packages do not need to conform to the global setting.
32db8b8
to
4ecc37e
Compare
Some packages in the repo (for example, the `actions` pkg) set a pre-release Dart SDK constraint so that preview features of Dart can be leveraged. This updates `aft` so that: 1) `bootstrap` skips packages which set this constraint if the current Dart SDK doesn't support it; and 2) Ignores preview constraints in the constraints checker, since these packages do not need to conform to the global setting.
Some packages in the repo (for example, the `actions` pkg) set a pre-release Dart SDK constraint so that preview features of Dart can be leveraged. This updates `aft` so that: 1) `bootstrap` skips packages which set this constraint if the current Dart SDK doesn't support it; and 2) Ignores preview constraints in the constraints checker, since these packages do not need to conform to the global setting.
Some packages in the repo (for example, the
actions
pkg) set a pre-release Dart SDK constraint so that preview features of Dart can be leveraged. This updatesaft
so that:bootstrap
skips packages which set this constraint if the current Dart SDK doesn't support it.