Scrum Report 4

[hawklu212]

Answer 3 questions:
○ 1. What did you work on this past iteration (2 weeks)?
○ 2. What were any major issues/challenges you ran into?
○ 3. What do you plan to work on for this coming iteration (2 weeks)?

[hawklu212]

Zhiyuan Lu

1. this last iteration, I worked on creating email verification for login and signup, persisting login via cookies, password requirements, integrating the login and preference Model to mongoDB, and preventing route access without certain login credentials.
   2.Setting up cookie verification and transfer was difficult as many things in the server such as the CORS allow policy, and the client curl credentials had to be adjusted to pass cookies across server/client. Merge conflicts were also an issue as the team worked on a lot of separate components but slightly adjusted each others components.
   3.Add in a profile display for current Preferences, and investigate how to deploy with hiroku

[FMuir]

Fraser Muir

1. This past iteration I worked on defining the way we would be evaluating route difficulty, helping design the models required for this, and implementing the rating system and passing the relevant data into the return payload for the front end.
2. Nothing too major in terms of challenges, though did experience difficulties with some conflicting models and dealing with fairly complex objects that could be frustrating to work with and required extensive debugging.
3. Finishing up all the final backend pieces, and finalizing decisions regarding our data design. Create an elevation profile image to be used with the display cards. Start familiarizing with deployment requirements.

[justinjao]

Justin Jao

1. The past iteration, I figured out how routes were actually represented in the GMA (summarizing results in a document for my groupmates), how to use the backend NodeJS client for making GMA requests, and wrote the code in the backend to make directions and elevation requests using this client, and wrote code to determine maximum elevation increase per route. I also designed components for use in the frontend to support Hawk's login work.
2. Upon further research into the GMA, figuring out how to potentially discover alternative routes that we could present to our user proved to be a bit too challenging as there was no immediate way to query for all roads available in an area without doing an expensive brute-force search (which didn't even guarantee high-quality results). We have since decided to table this feature until further notice.
3. Finish hooking up the frontend with the backend payload, add features to allow changing of the display of the map based on clicking of the cards, add the ability to save routes and save this on MongoDB, and begin cleaning up the UI for final presentation.