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
I have the following wizard setup, which looks quite natural to me and doesn't require the ConfirmAuthPage to do anything with GoRouter (thus, it can be safely moved around without any fear of breaking the flow):
The problem is that Wizard doesn't let me call next() from within the ConfirmAuthPage, which seems to leave me no choice other than introducing GoRouter routing right into the ConfirmAuthPage, which I'd want to avoid.
What do you think about adding an option to allow next() on the last page of the flow or even allowing it unconditionally (doing nothing if there's no next page in the flow)?
The text was updated successfully, but these errors were encountered:
I have the following wizard setup, which looks quite natural to me and doesn't require the
ConfirmAuthPage
to do anything withGoRouter
(thus, it can be safely moved around without any fear of breaking the flow):The problem is that Wizard doesn't let me call
next()
from within theConfirmAuthPage
, which seems to leave me no choice other than introducingGoRouter
routing right into theConfirmAuthPage
, which I'd want to avoid.What do you think about adding an option to allow
next()
on the last page of the flow or even allowing it unconditionally (doing nothing if there's no next page in the flow)?The text was updated successfully, but these errors were encountered: