Replies: 2 comments · 7 replies
|
We have a plan for this. In summary, in the next 6 months, we'll not only publish a new package |
|
Even though the new project can be used as a fork, it contains breaking changes compared to the previous versions. So make sure changes are addressed in recent usage. |
|
I am wondering if we should make 4.x branch without breaking changes that we can also release to pub.dev |
I can't get the point of creating old branches. |
|
I think it would maybe make it easier to move from |
I would say no from the very start. Changes are already happened and are hard to rebase again. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I still think this will be a hard pill to swallow for many projects and not easy to migrate as even in my projects, a lot of 3rd party libraries depend on
dio.I wonder if we can somehow provide a migration package that fuses
dioanddioxby only changing the backing adapters for aDioinstance. What do you guys think?All reactions