catcher
catcher copied to clipboard
jhomlala
Update to Flutter 3
Closes #216 Closes #217 Closes #227 Closes #229
Until this is merged, you can use this fork by declaring a dependency_override:
dependency_overrides:
catcher:
git:
url: https://github.com/ThexXTURBOXx/catcher.git
@ThexXTURBOXx - I'm curious, why did you up the compileSDkVerion to compileSdkVersion 32?
@michael-woolsey I always do that when I see an outdated compileSdkVersion in order to show that the library is in fact compatible with newer Android versions. When other users just copy paste the example, they might use an outdated version by accident then.
So, that specific change does not have something to do with Flutter 3 in particular, but is something that might be nice to have
@michael-woolsey I always do that when I see an outdated
compileSdkVersionin order to show that the library is in fact compatible with newer Android versions. When other users just copy paste the example, they might use an outdated version by accident then. So, that specific change does not have something to do with Flutter 3 in particular, but is something that might be nice to have
Thanks @ThexXTURBOXx do you know where the latest version is listed online? My GoolgeFu is failing me this morning and I just wanted to read up on it. :)
You're welcome :) They are (unofficially) listed for example here: https://apilevels.com/ However, SDK versions marked as BETA can not be used to compile APKs that are compatible with earlier versions. So, always be sure to use the latest full release.
@ThexXTURBOXx Just out of curiosity, is there a particular reason why you chose not to use the ambiguate approach?
@luvetter I don't really like that approach, it is messy code in my opinion.
Null-safe types are there for a reason, namely, they should never be null when you use them.
The ambiguate approach just transforms a type that cannot be null into one that could be null, i.e. you have the same problems as before, but shifted them elsewhere (into the ambiguate method).
It should be encouraged by respective libraries to update to Flutter 3 in order to support stay on actively supported versions :)
@ThexXTURBOXx Thanks, I understand, that's definitely better than supporting legacy code for an unknown period of time.
Nice fix @ThexXTURBOXx , can we please merge this and push a new version to pub.dev? Ping @jhomlala
Sadly, our dear author has had no activity since June 2022, and none of his open source code has seen maintenance. Maybe we can push Flutter to officially incorporate Catcher into the main repository for management, or create a new catcher-plus v1.0.0.
It really seems like there won't be any future updates here. I will release my fork to pub tomorrow.
This project was the best solution I could find for Flutter approx 1yr ago and have been pretty happy using it in a low/moderate usage application. Bit dissapointing to see it not be kept up to date. @jhomlala life got busy or moved on? Thankyou for your efforts anyway and @ThexXTURBOXx pub fork would be good temporary solution. Long term this project needs new ownership and at a minimum for @jhomlala to archive and update readme to the fork. What is the deal for "plus" community projects in flutter?
@hampsterx I am not planning to create a package just for a temporary solution. I would create it to keep it completely up to date from now on in all future Flutter releases. So, I would be the maintainer of a new catcher package from then on.
great @ThexXTURBOXx
https://github.com/fluttercommunity/plus_plugins
So what is the deal here, all of these are inside a single repo? Ugh..
Not sure you want to use "-plus" name, sounds confusing with above.
Plus plugins is a place for abandoned plugins to be updated by the community with proper support.
I will use the name catcher_2 instead. I have done the same for flutter_web_auth :)
catcher_2 for flutter 3. oof probably fine, originality is not my forte either :)
The _2 will just mean "continuation". Since I will update catcher also to flutter 4, 5 and so on there :)
The author did not appear on GitHub for half a year before, and appeared again in the past few days. This is a good thing, and we were worried about it at first. Maybe we can ask the author's opinion.
Hi 👋 sorry for my absence, I will merge it shortly and release it. Thanks everyone for pushing this topic (@ThexXTURBOXx especially).
Hi @jhomlala and welcome back! I was a bit worried something happened to you. Glad to see you back! In that case, catcher_2 won't be needed :)
@jhomlala Thank god you are back :-) And thank you @ThexXTURBOXx for keeping catcher up to date in his absence!