-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
Unify Analysis Options YAML into a single reference file (see #74) #84
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
Conversation
It's a massive PR, sorry, not a lot of lines changed but a lot of files. |
Could be done in steps one package at a time to make it easier to review? :) |
Maybe yes, in this case is because updating the version of |
Is the relative include from the repo root necessary? Would that break stand-alone packages downloaded from pub.dev? P.S. Do you know how
|
you are right, it is not necessary to have the file with the include except if you are specifying different rules, so I remove them all and just leave the root one |
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.
It's a big PR but the changes are very simple. I glanced quickly through and have only some nit-pick. Fix if you feel like it. :)
if (_singleton == null) { | ||
_singleton = Battery._(); | ||
} | ||
_singleton ??= Battery._(); |
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.
👍 Nice, I've been tempted to fix these
@@ -0,0 +1 @@ | |||
include: ../../../analysis_options.yaml |
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.
can be removed?
dev_dependencies: | ||
pedantic: ^1.8.0 |
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.
is this correct or should it be bumped to 1.9.2?
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.
well spotted, actually there's not even dart code on the macos projects so I think the dependency could be removed
Future<PackageInfoData> getAll() async { | ||
String url = | ||
"${Uri.parse(window.document.baseUri).removeFragment()}/version.json"; | ||
var url = |
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.
final?
for (math.Point<int> p in state.body) { | ||
final Offset a = Offset(cellSize * p.x, cellSize * p.y); | ||
final Offset b = Offset(cellSize * (p.x + 1), cellSize * (p.y + 1)); | ||
for (var p in state.body) { |
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.
final?
I am not sure why I got some analysis issues on my computer by they don't appear on CI, I created a ticket for that: #85 Besides, I am merging this now :) |
Thanks for reviewing @jpnurmi ! |
This PR unifies all projects
analysis_options.yaml
into a single one and upgrades pedantic to 1.9.2, fixing all new analysis issues raised.