Closed lukef closed 4 years ago
Hi everyone! I'm taking over the fluro
package from @lukef. Two Lukes? I know, it's a little confusing, but the good news is you don't have to learn any new names!
So what's happening with fluro
? Good question!
Router
class name collision and do a patch release on pub.fluro
to the new Pages / Navigator 2.0 API.First two items have been resolved and Fluro 1.7.0
is now on pub! https://pub.dev/packages/fluro
Great to see Fluro getting back into business. Have already used this powerful library in multiple projects. Looking forward to more features. Wish you the best!
赞
Hi Luke Pighetti,
i am so glad someone took over Fluro. It could become one of the most important packages for Flutter! Wish you all the best!
Hey @lukepighetti , glad to see someone taking over Fluro 💪 , perhaps one of my favorite libraries! As I am quite invested in it for my projects, if there is anything I can help out with, please let me know.
Quick update! I've been wanting to get this migrated over to Nav 2.0 / Pages API for a while now, but I'm still waiting on core Flutter to get a little more developed in this area before making the switch. I just learned today that built-in deeplinking has been added to Nav 2.0 and is currently in Flutter master
channel. Once this hits beta
I will have another look at the status of the Nav 2.0 API and see if it's mature enough for us to do a rethink/rewrite of Fluro to leverage deeplinking + declarative API.
@lukepighetti are you still planning to migrate this to the new nav 2.0? I find it incredibly complex, so if you can make nav 2.0 simple, I think that would be a big win.
Yes, this is definitely going to happen. I am still doing my research and waiting for a few things to fall into place before I make the push to migrate. The current idea is to push for an API similar to the Vue navigator API.
Good news. Fluro is moving to a new home.
Say hello to @lukepighetti! Luke is one of the most active, enthusiastic and talented Flutter developers there is. I'm glad it's going to a friend.
I won't get too deep into it but some of the policies adopted by the Flutter team have made it pretty much untenable for Yakka to personally maintain or develop this library. Constant breaking changes and, what we consider to be, generally less than ideal community consultation / collaboration have taken all the "fun" out of providing Fluro to you all.
I know many of you have already moved on or become frustrated with lack of communication and progress. I've, personally, obsessed over what to do with the project over many months. Many times I thought of shutting it down. However, I think there is still plenty life left in Fluro! There are still lots of cool ideas and everyone is excited for it to move way beyond what we envision.
Thanks for all your support!
Luke