Scrum report 6

[gshreya1999]

Tell us what you did, and what you would do next if you were continuing with the project work.

[gshreya1999]

Shreya Gupta:

• I finished up the tags functionality. I allowed adding tags while creating new posts and editing/removing tags in the edit listing feature.

• I displayed SOLD tag on sold items on homepage and individual listing page.

• I removed all sold items from the homepage listings, and made another section below it which showed 10 sold posts, based on when the items were posted.

• I added loading state to homepage, sold items, seller view and cart page. I also improved cart page UI.

• I added snackbar component on individual listing, to handle different response from server and show "added to cart" or "already in cart message"

• Added popup to ask user to sign in if they try to add item to cart/wishlist; removed these buttons if item was already sold

• If continuing the project, I would ensure that the user is not able to add their own items to cart/wishlist and can't go through the checkout with them

[SamSun0530]

Sam Sun: I built up the cart page and user account page with UI content, allow user to access from navbar I initialized cart items with add, remove function from homepage and wishlist page I added checking code to prevent duplicate items in cart I made webpage display with different user account I made the purchase history page, fetching data from backend I made user account page, fetching data from backend

[ivenadu]

Ivena Du:

• did prototype drawings for app
• registration page form / styling
• setup initial thunks for backend
• wishlist page functionality + styling
• search, sort, filter functionalities + style
• individual listing page
• deployed backend and frontend on Render
• backlog stuff: pricing style, edit listing form user input restrictions

If continuing the project:

• support adding multiple images for a listing
• implement pagination to not show all listings on the homepage at once
• improve UI style

[ndlee221]

Andy Lee

• Nav bar
• Checkout page
• Purchase successful page
• Setup db models and db connection
• Session handling: token generation upon login, store on client side browser, pass token as header for subsequent requests, retrieve associated user using middleware, expiry handling.
• Encrypt password (hash + salt)
• Resolve issues of cart buttons not working
• Resolve deployment issues
• Use Google's Address Validation API during checkout
• Concurrency handling of multiple users checking out same item at same time.
• Upon purchase, remove item from everyone's cart, mark listing as sold, add to user's purchase history.
• Backend routes and functions for login, logout, registration, purchase history, user account details

If continuing the project:

• Handle different timezones
• Save shipping details to user account and autofill by default on checkout.