Kaisel – Routes as Values. Dart 3 Native Router for Flutter

Posted by TheWiggles 2 days ago

Comments

Comment by written-beyond 1 day ago

Ignoring the claude-isms, this could be a godsend from the nightmare that is Go Router.

Comment by storywatch 1 day ago

The biggest issue with Go Router is that they keep changing the damn API. I can't believe the release cadence of a Flutter navbar library is faster than entire JS frontend frameworks like Next.js

Comment by rhmn_mdov 1 day ago

Very cool. Nav 2.0 should have been replaced by such a solution as soon as the sealed classes were introduced to dart.

Comment by rubiktubik 1 day ago

I like the ideas of the routing api. Could be my new favourite. Well done!

Comment by ifh-hn 1 day ago

I've read the quick guide and still don't understand what this is.

Comment by Yiin 1 day ago

it's a router that uses classes instead of strings, what is there not to understand

Comment by ifh-hn 1 day ago

I suppose what a router is, when it's not a tool or a network device. I assume classes as in object oriented?

Comment by satvikpendem 1 day ago

Honestly if you don't understand it, it's not for you as you're not the target market, which is fine, not everything is for everyone's use cases. It's a router in the sense of navigating pages in a Flutter application like /page-a, /page-b etc and instead of having them as raw strings, the routes are defined as classes like PageA().

Comment by ifh-hn 23 hours ago

Hopefully not since I'm actively attempting to learn flutter for cross platform development. I'm not a professional developer and am only just starting out with flutter.

State management confuses me at the moment. Seems overly complicated with way too many options. Actually a reason I'm going with flutter I atead of a web framework was too many options with no clue which is best. Seems navigation is that way too...