History, Navigation & Routing Issues (Flutter)

[alexadhy]

Favicon Issue(s)

• Put favicon.ico to maintemplatev2/client/web as it is not showing

Navigation (Routing) issues

1. Navigation stack seems to be restarted / cleaned on refresh (to be confirmed by @AppliNH )

Related Issue: flutter/flutter#59277

Steps to reproduce:

• TBD

2. On mobile (to be confirmed on desktop), navigation can get to unrelated routes / icons does not reflect actual route selected

Steps to reproduce:

• TBD

3. Survey Page needs to have both projectId and orgId in its url param

[AppliNH]

@Gutterbacon we have to discuss about keeping the modular routing or migrate to the regular one.
Unless we fix this... Except using a Provider pattern (which might be overkill ?), I don't see how to proceed

[joe-getcouragenow]

Adding other cross needs of the router that flutter modular provided to us, so you know the design needs before you break things.

• deep linking where a link is coped from one flutter web app ( or native app ) into another.
• url schemes where a flutter native app and open another flutter native app on desktop or mobile

Both of the above were verified to work ages ago, however we don't have the code in CI that shows this working liek we had before.

This is why we need dummy modules and dummy apps actually. So that we can verify that the Modular architecture works and keeps working. So once we get Booty, CI, CD running smooth, we should introduce dummy apps and modules so we can verify this works.

To test this we need to use some of the tools in Booty like screen shot, and other automation tools as part of E2E testing. E2E works well with dummy modules and apps because the data is small and it verifies the architecture.