Closed teosarca closed 5 years ago
This is going to be tricky the way things are laid out now. Translations are the first request, so probably easiest thing to do would be duplicating this request on enter action for reset password views.
i could live with that.... (talking about requesting again the messages)
Results of IT1 tested in release
User language is correcly considered in Forgot Password feature:
Is this a bug or feature request?
follow-up of https://github.com/metasfresh/metasfresh-webui-frontend/issues/1878 backend: https://github.com/metasfresh/metasfresh-webui-api/issues/1038
What is the current behavior?
Which are the steps to reproduce?
i.e.
GET /availableLanguages
is called => at this point we don't know user's languageGET /messages
is called => at this point we don't know user's languageGET /resetPassword/{token}
is called => now here we are setting session's language using user's language .....What is the expected or desired behavior?
GET /resetPassword/{token}
please usePOST /resetPassword/{token}/init
(see http://w101.metasfresh.com:8080/swagger-ui.html#/login-rest-controller endpoints).POST /resetPassword/{token}/init
before getting the/messages
because thatPOST
will initialize session's language.