Description
Hello.
Thank you for sharing this project and associated tutorial with us.
The end-results of your project doesn't match most of the structures I use in mobile. To stress here, this is because I'm used to specific app structure inherited from previous projects, rather than short-coming on your work. I tried to build on your work to find how I can implement the following:
- Accessing user's posts without using
navigateTowhich would jump the current user across tabs. - Getting to access post page from anywhere in the app, using one route only.
The first was quite straight-froward; I simply converted single-user route to a parent route including a child for posts route. Re-build, re-run and now I can get to access user's posts from his profile page.
Second point was more tricky. No matter what I did in attempt to push the same named route in current tab, I yielded errors. Lastly, I tried a behaviour that is common in react-native apps, which is keeping common pages as root-based routes, in which it results in the page covering the whole screen when navigated to from any page. I had to add an app-bar to get the back button. This worked, though this is not the end-results I would wish for.
Now, I want to hear your opinion on these:
- What do you think of this? Is this something that is prohibited in flutter-land for any reasons? Or, a welcome change?
- If you ignore my changes, how would you implement the requirements I listed in the beginning?
Thanks again for your work and looking forward to discussing with you this topic.