You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Bug report] This package will stop working on the upcoming stable 3.10 release #563
Flutter 3.9.0-0.2.pre • channel beta which is about to become 3.10 stable is removing API that was marked deprecated in the earlier Flutter versions. Very soon this package will stop working on the stable release because no effort is being made to remove deprecated API.
Is it possible that changes can be made to accomdoate for this so that testing on the beta channel can begin for apps that use extended_image - my initial checks would suggest nothing is breaking by fixing the API used to ensure they match the change method signatures.
But you're using methods that are already marked as deprecated. Why not do the work now so the package works whenever flutter upgrade - otherwise your package becomes a breaking package that causes delays and there's no need for that
Stable 3.10 release candidate has been released and yep, this package is breaking. All other packages I used (over 30 of them) have made changes BEFORE and removed deprecated API, but unsure why this package's author @zmtzawqlp is reluctant to do something proactive and fix things before it breaks. My only solution is to fork and make the changes myself. Took only 15 mins and surprising that the author isn't willing to help in that way - @zmtzawqlp is there any reason why you're not looking into this?
Activity
[-][Bug report] [/-][+][Bug report] This package will stop working on the upcoming stable 3.10 release [/+]zmtzawqlp commentedon Apr 11, 2023
only migrate it when flutter publish new stable.
gslender commentedon Apr 11, 2023
But you're using methods that are already marked as deprecated. Why not do the work now so the package works whenever flutter upgrade - otherwise your package becomes a breaking package that causes delays and there's no need for that
ps6067966 commentedon Apr 11, 2023
Yes, I can confirm.
This package is causing issue in master channel.
gslender commentedon Apr 12, 2023
Stable 3.10 release candidate has been released and yep, this package is breaking. All other packages I used (over 30 of them) have made changes BEFORE and removed deprecated API, but unsure why this package's author @zmtzawqlp is reluctant to do something proactive and fix things before it breaks. My only solution is to fork and make the changes myself. Took only 15 mins and surprising that the author isn't willing to help in that way - @zmtzawqlp is there any reason why you're not looking into this?
gslender commentedon Apr 12, 2023
This is the set of minor changes needed
lhengl@08c6130
eerive commentedon May 10, 2023
Flutter 3.10 stable just went live, please consider approving #572
AliSattar95 commentedon May 10, 2023
Flutter 3.10 stable is live, please approve #572
## 8.0.0
zmtzawqlp commentedon May 11, 2023
8.0.0 is ready on pub.
* Migrate to Flutter 3.10.0 and Dart 3.0.0 (#557,#563,#570,#572,#573)