Scrum Update 4

[HeinzUBC]

What did you work on this past iteration (2 weeks)? What were any major issues/challenges you ran into? What do you plan to work on for this coming iteration (2 weeks)? Name & CSID

[HeinzUBC]

CS ID: r4e1b Peter

1. What did you work on this past iteration (2 weeks)?

During the past iteration, I have done the following.

• I have implemented the MongoDB route handlers for the TODOList node backend
• I have updated the Redux toolkit reducers and React frontend given the MongoDB integration
• I have added userID attribute to both TODO item and Category
• I have added ability for users to add "Finished" tags to each TODO item
• In addition to choosing Date values, I have added the ability to pick time values for each TODO item
• I have added the ability for TODO list diaplay to show error message if user tries to delete category used by TODO items
• Fixed React components so that TODOList module UI is robust to screen resolution changes

2. What were any major issues/challenges you ran into?

The main challenge was learning to update the node route handlers using Mongoose so that it communicates with the MongoDB database. Another issue was trying to make the React components robust to screen resolution changes. It was a learning curve, but I was able to successfully reference examples online to figure out how to complete the update.

3. What do you plan to work on for this coming iteration (2 weeks)?

• I will work to add a "calendar" view of TODOs to my TODOList module. I need to find a suitable React component to achieve this.
• For the error message sent when attempting to delete a Category associated with TODOs, simplify the message to something like "This category is still in use and so it cannot be deleted."
• Resolve spacing issue for Dashboard view of TODO list. The “TODO List” title and the item counter are too close when list is empty.
• Prevent users to setting endDate with time values prior to the startDate value.

[awctw]

Annabelle Wang & c1s2b

I have worked on making the timer settings saved for each user through the database, allow users to edit their registered information (username, first name, last name, email), moving login and register to a landing page, and worked on real time messaging feature with Kush. Some issues I ran into were properly sessioning users, since I was storing in the local storage instead of session storage there were bugs when multiple users logged at same time. Another issue was properly storing the chat history and displaying it but I was able to resolve in the end. I plan on refining the chat feature with Kush and deploying the website in the next two weeks.

[AlanZhangDev]

Name: Alan Zhang csid: g2e2h

In this past iteration, I worked mainly on the habits functionality. Specifically, I implemented the ability to specify the specific days of the week each habit would occur, as well as an optional setting for the start and end times. To do this, I also installed the MUI X library for its time picker tools. I also refactored the habits functionality so that it would work with user IDs as well as use Redux. The major challenge I faced was trying to find a time picker component for the project, as building it custom would have taken a lot of time for little value, and Material Tailwind did not have any time pickers. For this upcoming iteration, I plan to fully flesh out the habits functionality; I am planning to add the ability to delete and edit habits, as well as implement a detailed habits page which would include a visualization that tracks the habits a user may have.

[kush458]

Name: Kush Arora csid: l8i3b

For the past iteration, I primarily worked on improving our flashcards feature and progressing toward checking off another one of our standard requirements. In particular, I worked on implementing the spaced-repetition algorithm to facilitate intelligent scheduling of flashcards. In addition to that, I also worked with Annabelle to add additional features for our real-time chat functionality. One challenge I ran into was while building the refresh API to refresh a flashcard's review date after a review, wherein I was correctly applying the algorithm but wasn't targeting the correct cards to be refreshed. For the next two weeks, I plan to work with Annabelle to refine the chat feature and modify the current styling to make it more uniform throughout.

[leungkenneth]

Name: Kenneth Leung csid: c4o1b

This past iteration I worked on improving miscellaneous aspects of the Gantt Chart (e.g. allowing for color changes, updating styling, etc.) and making it use Habit, TODO, and Category backends instead of sample data. One challenge I ran into was in reconciling the differences in implementation of the other functionalities in order to unite them into one chart (e.g. different date formats, different fields to display, etc.). In the coming iteration, I will be completing as much of the written requirement for the project as I can, further improving the Gantt Chart, and attempting to unify the styling of the app.