Please check if your PR fulfills the following requirements:
[ ] Affected Tests have been added/altered (for bug fixes / features)
[ ] Docs have been reviewed and added/updated if needed (for bug fixes / features)
[X] Build was run locally and mvn install succeeds
Pull request type
Please check the type of change your PR introduces:
[X] Bugfix
[X] Feature
[ ] Code style update (formatting, renaming)
[X] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):
What is the current behavior?
Currently there is no real check if the session is expired, it is only checked if the user seems to be "logged in" in the redux-state, however this does not reflect the real login state itself.
What is the new behavior?
Refactored ensureLoggedIn functionality to actually check the loginState
Removed the showTermsDialog that is pushed when no user is not logged in into the respective action
Refactored the ensureLoggedIn functionality to open a modal dialog asking the user to login or create an anon-account, and proceed with the chosen action (currently create or connect) as a "success"-callback
Changed the login function to send a login request even if the redux-state seems to have a logged in user
Login field for the modalLogin is fixed to the currently "logged in" user in the state (that way we can ensure that there is no other user login that might cause failed connects/creates
Pull request checklist
Please check if your PR fulfills the following requirements:
mvn install
succeedsPull request type
Please check the type of change your PR introduces:
What is the current behavior?
Currently there is no real check if the session is expired, it is only checked if the user seems to be "logged in" in the redux-state, however this does not reflect the real login state itself.
What is the new behavior?
Does this introduce a breaking change?