-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Refactor URL logic #3
Comments
This one I can fix if you approve my package for routing: https://pub.dev/packages/app_state If you care about maintainability, the largest app it was used is Apache Beam Playground: https://play.beam.apache.org |
I tried looking into this but gave up for now. Is it possible to have the navigation route update without actually pushing a new page? The entire app is actually just on one route. |
Or is it possible to listen for URL changes outside of the router? |
In theory, it is possible to listen to the URL change and do something instantly, and that is what Navigator 2.0 is all about. However, in my apps I have seen it reloading the app at the given URL, which is still better than reverting the change. I did not investigate further because reloading was OK for me. |
I'm fine with the page reloading when the URL is manually changed, but what I don't want is the app to try and navigate between states when the route is updated by the UI |
No, programmatic updates of the address bar do not cause reload with Navigator 2.0, just like it is the case now in the app. |
What I'm saying is if we wanted to use the navigator to go from package1 to package2 and we did |
This should be fixed on https://beta.pubstats.dev. Let me know if it works for you. |
Hey the navigation buttons work too and all I had to do was bypass the Flutter Navigator entirely 🙃 |
Closing since this appears to work |
Steps to reproduce:
Expected: Navigated to the new package.
Actual: The URL change is reverted, still viewing the old package.
The problem is from not using Navigator 2.0, and because the URL is parsed only once in
DataController.create()
inmain()
.The text was updated successfully, but these errors were encountered: