[image_picker] Depend on AndroidX Core instead of Legacy Support v4#1934
[image_picker] Depend on AndroidX Core instead of Legacy Support v4#1934cyanglaz merged 2 commits intoflutter:masterfrom ChristianKatzmann:image_picker_no_legacy
Conversation
|
We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google. ℹ️ Googlers: Go here for more info. |
|
CLAs look good, thanks! ℹ️ Googlers: Go here for more info. |
Co-Authored-By: Michael Klimushyn <mklim@google.com>
Description
It's not recommended to depend on the
legacy-support-v4artifact any longer as we should depend on the relevant sub-artifacts instead to reduce the transitive dependencies.The
image_pickerpackage only uses classes from theandroidx.corepackage, so we can safely replace theandroidx.legacy:legacy-support-v4dependency withandroidx.core:core.Related Issues
This simple change is part of the PR #1878.
Checklist
///).flutter analyze) does not report any problems on my PR.Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?