Use GoRouter redirects to handle app startup state changes #151
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Closes #150.
Motivation
While
AppStartupWidget
is a great way to initialize dependencies with eager provider initialization, particular care must be taken for apps that support navigation by URL or deep links.For those apps, the root-level widget must be configured immediately (with
GoRouter
or equivalent).To account for this, I've modified the
GoRouter
code as follows:Additionally, this PR moves the Firebase initialization code back in the
main()
function:This prevents any "Firebase app not initialized" errors that would otherwise occur
ref.watch(authRepositoryProvider)
is called inside the GoRouter body.Besides, the Firebase initialization code will only fail in case of a configuration error (which can be immediately spotted when running the app) - so it's best to keep this inside
main()
.