You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 20, 2022. It is now read-only.
The current implementation uses the old Navigator 1.0, and while it is not deprecated, it uses the imperative style and is very verbose. It also requires importing the other screen and constructing it manually, which breaks SRP.
Navigator 2.0 is more declarative and gives finer control over the navigation stack and isolates the job of navigation from the screen rendering.
This can be achieved using one of the following methods/libraries:
Manual: Writing the router delegate and router name provider/parser ourselves
For reference, the last instance of the router when it was written using Navigator 2.0 can be found here (It was removed in this commit: aabounegm/phrase_recorder@2e5ae90)
The current implementation uses the old Navigator 1.0, and while it is not deprecated, it uses the imperative style and is very verbose. It also requires importing the other screen and constructing it manually, which breaks SRP.
Navigator 2.0 is more declarative and gives finer control over the navigation stack and isolates the job of navigation from the screen rendering.
This can be achieved using one of the following methods/libraries:
The Flutter routing packages usability research report is a good starting point
The text was updated successfully, but these errors were encountered: