(#345) Set new dependencies to account for Flutter 2 requirements #346
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.
http_parser
anduuid
are transitively depended on in many packages, especiallylogging
, so this package must follow along with the dependencies.Still hitting a block with
analyzer
andover_react
, however.Fixes #345
Motivation
Since Flutter 2 has been de facto mandated since its release (by Google upgrading all its core packages and requiring users to do so as well),
w_transport
should be upgraded to match. However, the nature of dependencies with other Workiva-internal packages is making this quite difficult to do form the outside.Changes
New dependency version in pubspec.
Release Notes
Upgrade dependencies to enable Flutter 2 use.
Review
See CONTRIBUTING.md for more details on review types (+1 / QA +1 / +10) and code review process.
Please review:
QA Checklist
Merge Checklist
While we perform many automated checks before auto-merging, some manual checks are needed: