getx

getx copied to clipboard

Basicly the package is abandoned, and a lot of thinks that work in past are not the same. The last update is 2 months ago, so that only comprove my sugested, so bugs were found but the Getx Team don't fixed it. I cannot believe that the most famous package in flutter was simply ignored, please or you do something like call some people to help you or pass the administration to a active person. @jonataslaw

For sure everyone loves the package because it is very useful, robust and of course free, but also if the important functions starts to show some problems it needs maintenance and atention.

This is indeed a big problem. There have been a lot of undocumented breaking changes (Nav2 has been there for more than a year and has still no documentation), (It has introduced a lot of breaking changes even on the stable release). The package is not properly tested which makes it currently a bug bomb.

To be honest, the master version has a full state manager refactor, a full navigation refactor, and a full dependency manager refactor. I sincerely wish I had more time, and I will probably have it from the 16th of next month.

The reason I haven't sent getx 5 to pub dev yet is that: 1- he has no documentation 2- Navigator 2's nested navigation still has bugs 3- still need to rewrite the modals. Nav 2 introduced a bunch of issues into Flutter, such as: -It's impossible to use it without using the nav 1 api, especially for overlays. We need to rewrite the dialogs and bottomsheets and use a custom overlay to fix show them.

If anyone is willing to help maintain the library, I'm also willing to explain how each feature works and is built.

Well, i can help a bit if needed.

Was it not a bit too ambitious to refactor all of that? Will it haven't been easier to first test everything and then start to refactor? Was it a good idea to start to refactor in v4.6.5? and not wait for 5.0.0?

My main concern is that going into Listenable for _RxImpl from 4.6.5 introduced a major bug. It also means that #2518 (broken toggle) is still in 4.6.5.

Would it not be better to make sure v4 is stable, tested and documented before going to release v5?

@jonataslaw when you return, can you please work in #2336?

Well, i can help a bit if needed.

Was it not a bit too ambitious to refactor all of that? Will it haven't been easier to first test everything and then start to refactor? Was it a good idea to start to refactor in v4.6.5? and not wait for 5.0.0?

My main concern is that going into Listenable for _RxImpl from 4.6.5 introduced a major bug. It also means that #2518 (broken toggle) is still in 4.6.5.

Would it not be better to make sure v4 is stable, tested and documented before going to release v5?

There are also many opened pull requests

@jonataslaw when you will return to update GetX?

Can Getx ever bring context in future package versions? And still, make it the most simple state management?

To be honest, the master version has a full state manager refactor, a full navigation refactor, and a full dependency manager refactor.

I sincerely wish I had more time, and I will probably have it from the 16th of next month.

The reason I haven't sent getx 5 to pub dev yet is that:

1- he has no documentation

2- Navigator 2's nested navigation still has bugs

3- still need to rewrite the modals. Nav 2 introduced a bunch of issues into Flutter, such as:

-It's impossible to use it without using the nav 1 api, especially for overlays. We need to rewrite the dialogs and bottomsheets and use a custom overlay to fix show them.

If anyone is willing to help maintain the library, I'm also willing to explain how each feature works and is built.

@jonataslaw are you returning to active development of the package?

Looks like the package is abandoned 👎 .... probably time to start working on a major transition to something else

4.6.5 (7 months ago) / 5.0.0-beta.52 (5 months ago)

Or a major transition to a copy maintained by the community. Is there someone here with the "power" to approve pull requests and update on pub?

A leader is needed. There is talent willing to support the project but there is a lack of someone to manage it. Sorry for my English

This really needs @jonataslaw to support a transition. I'd put my hand up to lead and support this, but if Jonny isn't willing then it would be difficult to undertake

Best outcome is for Jonny to assign someone owner of the existing repo... still viable but hard to facilitate is the copy / fork and duplicate approach