This PR includes the refactored user data class, new navigation logic and all the refactoring needed for the tests.
For the user data class I added 2 new fields, those being : joinedAssociations and hasProvidedAccountDetails, for the following reasons:
It is now possible to see what associations a user is part of.
The latter is to ensure correct navigation logic. If in the user has not completed giving his account details but has verified his email, he will be redirected to the AccountDetails Screen instead of straight to Home.
Potential Risks:
The joinedAssociations Reference List might be desynced with the members Reference List found in the association data class. (We partly loose the SSOT concept).
This PR includes the refactored user data class, new navigation logic and all the refactoring needed for the tests. For the user data class I added 2 new fields, those being :
joinedAssociations
andhasProvidedAccountDetails
, for the following reasons:AccountDetails
Screen instead of straight toHome
.Potential Risks:
joinedAssociations
Reference List might be desynced with themembers
Reference List found in the association data class. (We partly loose the SSOT concept).