Scrum report #3

[mdatan]

Describe (for the project): (1) what you’ve worked on in the previous two weeks, (2) what you’ll be working on in the next two weeks, and (3) where you might have gotten stuck during the last two weeks.

[HryChg]

In the past two weeks. I did 70% of the reducers related to HomePage, EventDrawer, and EditPage. I designed it so that event saved by users are centered at one reducer where multiple pages would have access to. For the next two weeks, I plan on reworking the log of the Event Filter in the homepage as well as moving most default states in our reducer up to the server for persistent storage. The biggest obstacle for me was transferring external google maps react component to a redux store because I was unsure whether certain methods are from the third party creating the component or from google maps itself.

[shirleywbi]

(1) For the previous two weeks, I updated the ItineraryPage to take in data from the Mongo server and added markers and info windows to its map. I have spent a lot of time trying to get the login page to work - it currently displays but has some conditional issues. I also debugged the currentDrawerReducer because it was creating duplicate divs every time we left the page and went back. (2) For the next two weeks, I will be working on the login page and the different screens people will see when logging in. (3) I got stuck on the login page over the last two weeks because of the built-in templates and trying to figure out how to call the methods. I also had trouble trying to get the server working because we removed autopublish and didn't publish the mongo data to the client. Furthermore, I had a bug with my ItineraryPage when trying to set up the reducers because a reducer store called "date" was created and I had used a this.props.date.

[mdatan]

• I created a reducer to store current events for a certain date and switched to Yelp's api to store a list of events when I realized that we could not get the correct time from scraping events from todocanada
• In the next two weeks I will be working on initializing the events based on the default date from Yelp's api and storing the events in the database instead of getting our events from the initial state in our redux store
• I got stuck with scraping the time from todocanada and decided to use an api instead for getting our events. I also got stuck on rendering the markers on the map based on the list of events in the currentEventsReducer but Harry fixed the issue. Right now I'm facing an issue with initializing the redux store state with an async function which is returning undefined and breaking the app so I will continue to work on calling the api from the server instead