Created option on router to toggle args generation

[carlosfiori]

Fixes #510

[carlosfiori]

@Milad-Akarie

[carlosfiori]

@Milad-Akarie can you review? I created this flag to have the ability to generate the args in a separated package, and export them

[carlosfiori]

@Milad-Akarie

[carlosfiori]

Just added some docs about this new flag in the README, @Milad-Akarie can you review?

[Milad-Akarie]

hey @carlosfiori I'm really sorry for my late reply. I don't understand how the router would work without the arguments. can you please explain it to me.

[carlosfiori]

Hi @Milad-Akarie thanks for reply

In this case, I have two app routers, one in a micro app (subpackage) and another outside. Both generates routes, but only the micro app router generate args The outside app routers are responsible to make navigation between micro apps and the one from micro app is responsible to navigate internally. The args generated by the micro app is exported and when need used by the outside app router. If is generated in both app routers, the error below can occur

[carlosfiori]

Hi @Milad-Akarie Basically in one app router will generate args and the other will not Other people are also facing this issue as in #510

[carlosfiori]

Hi @Milad-Akarie, I just update this PR with latest master.. Was I able to explain the need for this functionality? Was there any doubt?

[carlosfiori]

Hi @Milad-Akarie, I just update this PR with latest master.. Was I able to explain the need for this functionality? Was there any doubt?

[carlosfiori]

@Milad-Akarie

[carlosfiori]

Hi @Milad-Akarie, could you review this please?

[pedromneto97]

Any update? @Milad-Akarie