-
Every feature should have its own branch.
-
Every feature should have a F#Id.
Ex: F#12: Crud Routes - debugged for all products jsons
-
Commit often as possible, reffering the current feature in the commit.
-
If there is branch ready for a pull request at the end of the day, the GitMaster should merge it with the master.
-
Every feature branch should start with its feature Id
- Product Model
Id Name Description Price ImageUrl rating (maybe later) instructor (maybe later)
- Product Api - CRUD Methods
Ex: api/products/
- All Products Component/Reducer
Ex: /
-
Hobbies Seed
-
Single Hobby Component/Reducer
-
checkout will add association between user & products in cart (will place productId)
-
assocation: Product.hasMany(User)
-
after checkout, user has access to Product view (which would be the hobby woodworking class as example)
-
Note: each product (ex: hobby class) should be it's own model. So one for camping class, one for cooking, one for hog wrestling, joint rolling, etc.
-
User have associations with the Purchase model
-
User have associations with the cart model
-
Can Select products and add to card
-
Can view the cart
-
Can remove items from the cart
-
Can checkout the items from the cart
-
Can view its past purchases
-
Have a profile component
-
Have its own reducer on store
-
assocation: User.hasMany(Product)
-
Holds selected items
-
Has a total Price
-
A cart component to view the selected items
-
A cart can be checked out/reset
-
Have a smart tax calculator
-
Have a redux
- To be defined
- To be defined