Closed jschr closed 7 years ago
Isn't the token so unique that there is no need for userId? Or is it a optimization thing?
You can merge it either way. hmm how does the review thing work, can't find a way to access it :D
It's just because currently the route for updating includes the user id: users/:id/changePassword
. The token is unique enough and in fact contains the user id but the frontend ideally shouldn't need to decode the token.
Need user id in the email links and also made emails slightly nicer.