Currently, the API generates email confirmation and password reset links using hardcoded paths on the server side. This approach assumes a fixed structure for client-side routes, which may not always align with the actual paths used in the client application. To make the system more flexible and adaptable to different client configurations, we need to allow the client to specify the paths for email confirmation and password reset links.
Currently, the API generates email confirmation and password reset links using hardcoded paths on the server side. This approach assumes a fixed structure for client-side routes, which may not always align with the actual paths used in the client application. To make the system more flexible and adaptable to different client configurations, we need to allow the client to specify the paths for email confirmation and password reset links.