aws-amplify
[Feature Request] Custom paths/routes for Authenticator UI components
Description
As a user, I expect Authenticator library's to behave properly according to the platform and support custom routing/paths. Right now the navigation strategy of the Authenticator library is not exposed to the user to be customised. This brings the following problems:
- On web URL does not update according to the page changes
- Deep linking to a certain page is not supported
- Changing to an alternative way of navigation (e.g. using go_router or Navigation 2.0) is not possible.
Screenshots
Hey @Jordan-Nelson Just adding a comment to this issue, to see if there is any sort of update in regards to go_router and or navigation 2 support with some documentation to follow. As it has been already a year with out any progress on this. At a point where a project I am working is requiring a move towards navigation 2 for some feature support and with the use of Amplify, wondering what the best course of action is here.
Hi @TJMusiitwa, we do not have any updates. This issue is still in our backlog. Until it's picked up, these features will be unsupported.
