Fix issues brought up by pub.dev score analyzer #1088
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
LGTM. What line length limit are you using? Just so we (I) can use the same in the future and it's not so easy to get formatting-only changes in PRs. |
erickok
approved these changes
Jun 14, 2022
|
I just have it set at the default (80). Not my favorite, but probably easier to encourage others to format code in pull requests if we use the default options. |
|
Yeah same - not my fav but probably the best choice for the project. 👍 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This pull request touches on a lot of files, but the changes are almost entirely cosmetic:
Documentation comments
Running
flutter formaton all filesAdding barebones "example" directories to the subpackages
Upgrading the
numerusdependency.Upgrading
pubspec.yamlsubpackage descriptions.