Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

6/25/2023 Scrum Report #18

Open
shuting-hu opened this issue Jun 24, 2023 · 5 comments
Open

6/25/2023 Scrum Report #18

shuting-hu opened this issue Jun 24, 2023 · 5 comments
Assignees

Comments

@shuting-hu
Copy link
Collaborator

No description provided.

@michelleykim
Copy link
Collaborator

Michelle Kim (k3x2b)

  1. I worked on implementing redux actions for add and removing players as well as minor frontend css changes for better responsiveness.
  2. I had a bit of a struggle with redux state not properly updating between pages, but I was able to figure out the problem with some google searches.
  3. I plan to continue improving and implementing the frontend components and connecting backend and frontend states.

@martincai8
Copy link
Collaborator

Martin Cai (m5z8p)

  1. I worked on setting up image storage using google cloud storage and implementing an upload service in our app.
  2. Michelle and I realized that the way that we setup our server and our connection to MongoDB was not robust, since it was possible that the app would be started before the connection was established to our database. To fix this, we implemented the singleton design pattern and made sure that the app would only be started after the connection was successfully established.
  3. I plan to finalize the image uploading service and work with the rest of the team to connect our frontend and backend.

@shuting-hu
Copy link
Collaborator Author

Shu Ting Hu (a9k2b)

  1. I worked on setting up and implementing redux actions for fetching and adding sessions and players. I also built the game waiting room / lobby component.
  2. Setting up redux had a couple hiccups with the create store but was otherwise smooth once fixed. Since the client side and server side were not yet linked and the teams were still working separately, hardcoding data to the client side required some thought on best way to represent it for the demo even though it'll be moved to server side for our next iteration.
  3. I plan to work with the team to connect client and server, updating the redux actions to make api calls to the BE for data.

@michelle-wangg
Copy link
Collaborator

Michelle Wang (i5p4s)

  1. I worked on user authentication using Firebase and connected it to the front end for Google sign-in.
  2. Martin and I had a bit of a problem with the server connection to the database as the application might start before the connection is established. We were able to resolve this issue by using the singleton design pattern.
  3. For this next iteration, I will look more into security, finish user authentication, and help the team connect the frontend with the backend.

@VDeshh
Copy link
Collaborator

VDeshh commented Jun 26, 2023

Vishal Desh - CSID: w6y2b

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

Worked on Sign up page, integrating components to pages and cleaning up component designs to make them look better.

2. What were any major issues/challenges you ran into?

Not any major challenge this sprint as it was less workload on the frontend except the redux actions.

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

I will help integrate backend to frontend. Make Canvas quadrants dynamic. See how we can extract one strip of the canvas and overlay it for the next quadrant.

Backlog In Progress In Review Done
Final Page (Started by Michelle Kim Today) Mongo DB Setup Canvas Element Major Components (Eg: Canvas) / Oauth

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants