Scrum report #3

[tendy-s]

Each individual needs to post their scrum report as a comment on this issue:

**Questions your comment should answer:

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)?**

Rubric: 2: Includes all 3 points. Demonstrates a bit of meaningful reflection on at least one item in the report. 1: Simplistic, or no meaningful, specific information. 0: Missing or Late.

[tendy-s]

Name: Tendy Su csid: f7p0u

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

This past iteration I refactored our previous redux code to include relevant actions (e.g. the ability to submit a review and an image, set user preferences) and incorporate a parkSearchInfo slice and thunks for fetching details from our national parks API. I also implemented our second workflow for our landing page, which allows a user to search for their city and choose the distance they're willing to travel.

What were any major issues/challenges you ran into?

Refactoring required a bit of time and initially, I created new bugs; but through using Chrome dev tools and various console logs, I was able to resolve the issues. Also, at first I was unsure how to use Google's Places API but after looking at tutorials and through my own experimentation, I was able to successfully incorporate this component.

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

For this coming iteration, I plan to implement the ability to edit/delete reviews, integrate the frontend with the backend (e.g. populate components with the appropriate information from our database and ensure sorting/pagination work as expected), and assist with creating a login page.

[betternick]

Name: Syed Waqar Ahmed CSID: a2o6b

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

In this past iteration, I worked on building out the backend functionality for the user story where users can search for national parks by distance. I built the router, controller and DAOS for this functionality. The frontend passes the city of the user and the user's distance preference as query params, and the backend finds and returns those parks that satisfy those criteria.

What were any major issues/challenges you ran into?

Finding a suitable geolocation API that was free and would be reliable took some time. Also making tests for my backend functions which make external API calls proved to be a new challenge, however I was able to test it using mock HTTP objects using "node-mocks-http".

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

For the coming iteration, I will be adding functionality to sort the results according to sorting params received from the frontend. I also want to optimize the run times of my functions and do testing with Postman to make sure it is working well. I will then move on to implementing user profiles. This will involve learning more about tokenization and how to implement it.

[dong-michael]

Name: Michael Dong CDIS: f2m2e

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

I worked on writing the logic for parks and activities controller as well as the DAOs. I also dedicated time to setting up express in the back end, and debugging/ testing endpoints with Postman

What were any major issues/challenges you ran into?

Changes to the existing schema of the collections inside the DB required modification the API we used grouped the data in a way that was not easily accessible for what we were trying to do. This should we resolved soon as database is repopulated.

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

I plan on continuing to work on finishing current endpoints (e.g. sorting), creating new ones as needed, and working on modifying the database schema. I also aim to have the endpoints ready for this iteration so that integration with the frontend can begin.

[h-xi]

Name: Has (Hai Xin) Xi CSID: z3j4e

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

In this past iteration, I worked on building out the backend functionality. I peer-coded and mentored my teammates in the set up and design of the backend system. I built pagination logic for backend.

What were any major issues/challenges you ran into?

Figuring out the pagination logic involved some relatively more complicated arithmetic.

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

building out granular user authorization and authentication. Implement logic for sorting and filtering

[babakhadady]

Name: Babak Hadady CSID: y9m6h

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

I worked on adding various features such as adding a map, alerts and a favouriting system. I also worked on polishing some styling and updating a few features, such as dynamic park images.

What were any major issues/challenges you ran into?

At first I was using a google api for the map, however learned to discover that it wasn't free, so I had to scrap my implementation and learned to use openstreetmap instead.

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

I plan on polishing more of our frontend styling, adding some options on the search page such as filtering and also implementing pagination and connecting our frontend to our backend endpoints once they are ready.