chore(association/profile): implement passage of selected association's uid to the association profile screen

[Zafouche]

Description

• Implemented the receiving side of the argument passed through the Jetpack Navigation in MainActivity.kt.
• Implemented the sending side of the passage of argument in the explore screen Explore.kt.
• Added a helper function named findAssociationById in AssociationViewModel.kt, which fetches the Association object if it is present in the list of associations.
• Added the AssociationProfileScaffold composable in AssociationProfile.kt, which allows us to either display and error Text if the association is not found, either the data (for now just the acronym) of the association in the same scaffold.

Motivation

This PR implements the method of passing the selected association's uid to the association profile screen using Jetpack Navigation arguments. This approach follows what's explained in this article. This allows us to get the data of the association profile that has to be displayed on the association profile screen (AssociationProfile.kt)

Considerations

• Helper function in AssociationViewModel: I wrote a helper function within the view model to fetch the data with the association's uid. However, I am not sure about this approach. Say the user refreshed the page, we would need to re-call the function and convert the val association to a var. This feels unnecessary as it would change automatically if we used a state flow in the view model.
• Bootcamp approach: I'm considering the usage of the method that we implemented in the bootcamp, e.g. we have a function that selects a ToDo from the MutableStateFlow list present in its view model (which we have in our association view model), and the data can be fetched through another MutableStateFlow, where selectToDo stores the item from the MutableStateFlow list. Now I am not sure about it as I need to do research on it, but would the selectedToDo MutableStateFlow update itself if the MutableStateFlow list is updated? This could happen in the scenario of when the user was offline and gains back connectivity. This can seem far fetched, but the automatic update could be useful.
• Advantage of the usage of argument: If there is an event displayed on the profile, an event that is co-organized by multiple associations, and if we decide to make the small association logos clickable, meaning it would send us to their profile, passing the uid by argument might be best. This is because it would only get the data when the navigation system initiates the navigation to the new screen, however if we have the selection of the association like the selection of a ToDo in the bootcamp, first you would select the ToDo, then navigate. The selection might force the current composable to be redrawn (because it is a state flow), and then navigate to the new one, where it would be yet again redrawn. I am not sure about this, I need to do some research on it, but if this is the case, then it is not something we would want. Edit: From what I understand in the documentation, this shouldn't happen so this isn't really an argument.

Note

You cannot yet play around with it, as the view model is not yet used in the explore screen. I will work on using it on a different PR, and come back to this one, pull the changes on this branch so we can test this by hand as well. Tests are also not yet written as I am not sure this method is better than the one used in the bootcamp.

[Zafouche]

None of the tests have been tampered with as I need opinions on which method we should use.

[Zafouche]

I will sync this branch with the main branch.

[Zafouche]

I ended up simply changing the String value of the ASSOCIATION_PROFILE like @oskar-codes suggested and added the helper function the Screen object. More tests are yet to come.

[sonarcloud[bot]]

Quality Gate failed

Failed conditions
66.9% Coverage on New Code (required ≥ 80%)

See analysis details on SonarCloud

[Zafouche]

Not sure what else can be tested. @Romainhir will need the changes done to implement the association profile screen further. Does this look good for you to merge? @oskar-codes @Redd87