fix(package_info_plus): fixed deprecation warning & updated dependencies#442
Conversation
|
I just updated main branch can you please update with |
I will but before merging, should we remove the deprecated registerwith function, or just leave it in and annotate so it hides the warning? Because whatever we chose, we should apply it to all other packages aswell. |
|
Well, I'd say if we have a solution to replace it with a new API, let's do that, that much better, however, if we don't lets at least annotate it so later we will remove depreciated API and replace them with a new one. I prefer to implement a new API if possible. |
|
Currently v1 embedding with |
|
@juliansteenbakker
https://flutter.dev/docs/development/packages-and-plugins/plugin-api-migration#upgrade-steps @mhadaily |
|
@nohli It's more a question of choice i think. The flutter team encourages everyone to upgrade to V2, and right now only 20% of the projects use V1. You can keep providing support for V1 but where are you going to draw the line? Besides that, is it even possible for Flutter applications that only support V1 embedding to also support null-safety, like all packages here does? |
|
@nohli You can close your pr for this package. I'll update this to leave the registerWith in it if thats what we're deciding. |
|
@nohli @juliansteenbakker let's discuss there and make a decision, I don't think it's very critical to support V1. what we can do we can remove this and release a new Major version for packages so if anyone likes to use older version so still, they can but we will not support it? what do you think? question for you @nohli if you think this PR is covering your PRs, let's close yours and focus on this one if you agree? |
|
@juliansteenbakker build failed, I think you need to rebase with |
|
Already closed. So you want me to close all the other PRs, and open a new one, removing the registerWith method, for all other packages? |
|
@juliansteenbakker PR is merged. btw, since we have now this PR #495 do you think your PR will be still valid? |
# Conflicts: # packages/sensors_plus/sensors_plus/test/sensors_test.dart # packages/sensors_plus/sensors_plus_platform_interface/test/sensors_plus_platform_interface_test.dart # packages/share_plus/share_plus_platform_interface/test/share_plus_platform_interface_test.dart
Yes because that PR doesn't contain changes for package_info_plus. Also, this PR solves other deprecation problems besides embedding V1. |
|
@mhadaily this is ready to be merged |
|
@juliansteenbakker could you also use |
It is not in beta since yesterday, but I would be careful with pushing to 31, because it has some behavior changes. For example, |
|
@nohli Android 12 is not in beta anymore. Besides, when a new number is available in |
We should migrate and check every package individually. That is why this PR is only about package_info_plus. |
Yes, agree here. My message was mostly to @nohli since he has one big PR with changes to multiple packages, so I wanted to bring attention to that moment about Android 12. |
Description
This PR removes the deprecated embedding V1 from package_info_plus. Besides that it updates the dependencies and fixes a deprecation issue with regards to
getBuildSignaturemethod.Related Issues
Probably fixes #301
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?