A fitness tracking/logging application with social media aspects. The purpose of Resolute is to encourage users and their friends to be involved in each other's fitness endeavors through non-intrusive mobile notifications.
This was a big one. The goal was to add a page for a user to handle all their incoming friend requests. This included adding a new fragment that was linked to a new .xml file. Include a testing file to make sure that the navigation / the functionality of created buttons does what its supposed to.
Summary
Started by making sure that buttons could navigate to and from the friend request page.
Then did some work making sure that we could display a table (used a lot of code from Victoria's previous work. Thank you!)
After that committed some code that allowed for the table to be populated with a specific users friend request collection.
It was here that i noticed an issue with how friend request were being sent (already addressed otherwise i would tag again)
Committed some code that allowed for buttons to be generated dynamically for each row.
Then added listeners that would both remove the row when either was clicked. And then depending on which button was clicked it would either 1. Delete the request from the Users Incoming Friend Request Collection or 2. Do that exact same thing as well as move that requesting User into the Current Users Friends Collection.
Finished by writing some tests for navigation and row deletion when buttons are clicked
Overview
This was a big one. The goal was to add a page for a user to handle all their incoming friend requests. This included adding a new fragment that was linked to a new .xml file. Include a testing file to make sure that the navigation / the functionality of created buttons does what its supposed to.
Summary Started by making sure that buttons could navigate to and from the friend request page. Then did some work making sure that we could display a table (used a lot of code from Victoria's previous work. Thank you!) After that committed some code that allowed for the table to be populated with a specific users friend request collection. It was here that i noticed an issue with how friend request were being sent (already addressed otherwise i would tag again) Committed some code that allowed for buttons to be generated dynamically for each row. Then added listeners that would both remove the row when either was clicked. And then depending on which button was clicked it would either 1. Delete the request from the Users Incoming Friend Request Collection or 2. Do that exact same thing as well as move that requesting User into the Current Users Friends Collection. Finished by writing some tests for navigation and row deletion when buttons are clicked
It all works.
Should close out / wrap up Issue #34