Scrum Report June 27

[vandyliu]

(0) Write down your CSID (1) what you’ve worked on in the previous two weeks (2) what you’ll be working on in the next two weeks (3) where you might have gotten stuck during the last two weeks.

5 sentences

[vandyliu]

x8s1b

1. I worked on adding actual data from the spotify web api. I set up one endpoint on the backend to get the songs and also added login via spotify so we could have authorization to get information from the spotify web api.
2. I will continue to be working on adding more endpoints, and adding more calls to the spotify web API. I will also likely work on adding more components to the frontend to display the information we get from the backend.
3. I had a lot of trouble setting up the communication from frontend to backend to spotify web api and vice versa. It was tricky because there were a lot of communication details and protocols to follow, and if I messed up a small little thing, it was hard to track down. Luckily, I gained a little experience using a debugger and that helped me track down my problems, and solve them quicker than what I am used to.

[ianmah]

i1t1b

1. I worked on creating the darkmode ability using styled components and a theme provider. I also added the ability to add a user object to the redux store.
2. In the next two weeks I want to help out with the backend scraping and storing of user data in the database.
3. It was a fun and interesting problem to add a darkmode toggle. I had to do some refactoring so that components were more consistent in using styled components (instead of css files, which can't use the styled theme). And then once it was refactored to use styled components I had to create a theme provider, which was interesting because it didn't work at first. Once it was working had to make sure each styled component used theme values for their colours so that they were consistent with the rest of the app.

[adindotdev]

u1j1b

1. Set up redux and defined the boilerplate pattern we'll use for state management
2. Next two weeks I want to help build more components and define function stubs for backend->frontend.
3. Redux is a lot of code for what it does, but it gets the job done. Without a lot of experience, it's easy to get lost in the sauce of how things work and/or are supposed to work. I worked through those woes by starting with the idea and working backward to the tech: let's have dark mode, need a place to tell all components that we're using dark mode, redux can do that for us.

[calhong]

(0) Write down your CSID i8t1b (1) what you’ve worked on in the previous two weeks I worked on the friends sidebar icon component as well as the sliding pane component. I also worked through some of the older components and did some refactoring for code readability and reusability. (2) what you’ll be working on in the next two weeks For the next two weeks I hope to work on more components, fully fleshing out a lot more of our minimal requirements. I also hope to get involved on the backend setup and endpoint stubs from frontend to backend. As well work with the team to relook at our goals and planning out the remaining work. (3) where you might have gotten stuck during the last two weeks I would still consider my CSS experience as weak, so when my task this week was to fully animate a sliding pane sidebar I was very stuck in figuring out the animations needed and what I would need to trigger it. I was able to generate a hiding and showing modal, but on animations I was completely stuck. I ended up having to do a lot of research to figure out how to do it, only to find that someone had made a library that was exactly what we needed, and was able to link everything from the states I created earlier to accept the new component.

[huangsamantha]

r2l1b

1. Set up a Graph component for us to use on our insights page.
2. I will be building out more components and fixing icons, specifically I'd like to work on being able to change user settings.
3. I used a new library called recharts to build the Graph component. Thankfully the documentation is very good so I was able to follow along, but it did take me a while to figure which features would fit our uses the best. Looking into all the various options was cool because there's so many powerful tools out there but also made me realize how everything has benefits and tradeoffs, and it can be difficult to determine which ones are most important for your purpose. Also, integrating state management took a while with a lot of debugging.