Scrum Update - June 12

[danyliu9]

csid: p8s1b

This past sprint I helped complete our initial mockup wireframes for most of our UI interfaces. I also finished working on the post creation UI.

Next sprint I'll be working on adding functionality to the post creation UI (adding data to our mocked database) and extracting tag functionality to be used in multiple places.

I got stuck at a strange bug where my npm/yarn would fail to install my dependencies when I was first setting up. The code that was installed in my "node_modules" folder would be encoded incorrectly, and have strange symbols that would not compile. After many reinstalls of node.js, yarn, etc., I eventually created another Windows account on my PC and that solved the problem. I've run into a lot of bugs in the past, but I had no idea how my yarn couldn't install my dependencies properly on one Windows account and not the other. I think I should have tried a higher level fix from the start.

[jpfranci]

csid: e1r1b

This past sprint, I setup our codebase with the libraries we needed and with some examples of how to use it, including an example component and a way to test React components in isolation. I also worked on setting up the actions bar, where users can perform actions such as filtering and sorting.

Next sprint, I will help setup our backend codebase using node.js and creating easy build integration with our client pipeline.

I got stuck using a library, which I haven't set up before lerna, which allows you to run scripts on multiple packages (both client and server) with command. I also integrated some pre-commit hooks to our work, which I spent more time on because I hadn't done it before.

[srhsrhsrhsrh]

csid: s3n1b

This past sprint I helped with our initial wireframes for the UI and started on implementing the map and navbar components. For the map component, I worked on extracting data about location using the Google Maps API and connecting it with our redux stores.

Next sprint, I will make some fixes to the map component and add more capabilities to the navbar, as well as help with implementing server functionality.

I got stuck when connecting the location from the map to our mock database because of a silly typo :P It was also difficult to decide when and where to store location data as the user interacts with the map component. It will most likely still change as the app is being developed.

[dryu99]

csid: j2x1b

This past sprint I helped create some mockup designs for our core components on figma. I also setup our project's redux configuration and implemented some reducers and actions. I also setup a mock database using json-server.

Next sprint I'll be working on cleaning up some of our service modules and making sure sorting/filtering works properly for posts. I'll also be working on improving the general design of our posts view.

I had trouble deciding where to put some redux actions, given the fact some of the reducers seemed somewhat coupled (e.g. upvote/downvote in post reducer or user reducer). I settled on separating actions based on the primary state they were updating.