11–14 of 14 posts
Ignoring the claude-isms, this could be a godsend from the nightmare that is Go Router.
Earlier quoted context omitted.
it's a router that uses classes instead of strings, what is there not to understand
I suppose what a router is, when it's not a tool or a network device. I assume classes as in object oriented?
Earlier quoted context omitted.
I suppose what a router is, when it's not a tool or a network device. I assume classes as in object oriented?
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().
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...
Anyway thanks both for your replies, seems I've a lot to learn.