SOLID POD: Improve forward & back navigation
@cdawei is already working on this.
Since May 28, 2024.
- Dominant language
- Dart
- Stars
- 10
- Forks
- 7
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 6
Description
Navigation in solidpod is implemented often by providing a child widget as an argument of the constructor of a widget, so that the user will see the child widget once the work of the current widget is done.
When there are more than one out-going routes in a widget, e.g. in the POD initialisation widget, if the user click SUBMIT, it goes to its child widget, but if the user click LOGOUT, it goes to the child widget of the LogoutPopup, and these two child widgets are not necessarily the same. As a result, when constructing the POD intialisation widget, we may need two child widgets which does not seem to be a good approach (this may contribute to the problems described in #157).
This issue is for us to propose an improved navigation design in solidpod that can naturally support multiple out-going routes in a widget.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.