Why Arguments class are not generated for single parameter Widget? about auto_route_library HOT 6 CLOSED

Hey @fedotxxl is there a good reason why we should do that? I'm not sure if it's helpful

from auto_route_library.

Why did you choose only after one more param you generate Arguments class? May be 2 params is also simple? It's unexpected that for X params system works one way and for Y - another.

You know this behavior and you are ok with it. But I preferer always use Arguments class because:

• it makes code clear
• I wanna use the same approach everywhere and don't think "Does my page have single param or 2+?"

from auto_route_library.

You know this behaviour and you are ok with it.

I mean when you know something you don't see any problems with it... After 2-5 apps I will also just use it without any worries... But now (when I'm new to API) it looks strange for me. If it's a technical restriction then I'm totally ok with the current version. If it's just to remove if (paramsCount > 1) - I don't understand why not just to remove it

from auto_route_library.

as I said for the sake of simplicity, But I guess you have a valid point.

from auto_route_library.

FWIW, I also stumbled over this recently. It took me ages to figure out why it wasn't working... it was only when I started poking around in the generated code that I realised what was going on.

from auto_route_library.

@fedotxxl @edwardaux Even single parameters routes will have their arguments holder class now, Check it out!
auto_route: 0.4.3
auto_route_generator: 0.4.3

from auto_route_library.