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

Lak, Jeta, Ross, Yaz #37

Open
wants to merge 507 commits into
base: master
Choose a base branch
from
Open

Conversation

saintmedusa
Copy link

Assignment Submission: bEtsy

Congratulations! You're submitting your assignment. Please reflect on the assignment with these questions. These should be answered by all members of your team, not by a single teammate.

Reflection

Prompt Response
Each team member: what is one thing you were primarily responsible for that you're proud of?
Lak - cart + order styling, products, testing, jira board, homepage, styling of validation messages, and reviews
Yaz - cart functionality, detailed validation errors for order-items and orders, controller testing, the erd, product stock, merchant-orders dashboard view
Ross - Merchant, styling, oauth, testing models, homepage, review tests
Jeta - Category, styling of validation messages, views, 100% test coverage
Each team member: what is one thing you were primarily responsible for that you would like targeted feedback on?
Yaz - my structure for order-item/order/product validation/update in models when order is submitted/cancelled
Lak - bugs that emerge when features destroy-product-as-merchant and the cart operate in unison
Jeta - category testing, product controller testing
Ross - testing with session, is there a more efficient way? oath testing
How did your team break up the work to be done?
Initially we broke the project up by models - merchant for Ross, product for Lak, orders for Yaz, and Category for Jeta. Once we got the foundations of the MVC down for each model individually, we started collaborating more on the cross-model functionality, testing, and styling.
How did your team utilize git to collaborate?
We operated on local branches and the used the git website pull request/merge system to merge our local changes to master. Occasionally, we worked on the same origin branch simultaneously.
What did your group do to try to keep your code DRY while many people collaborated on it?
Yaz would go in after things were working and dry up code. Lol, actually we don't know
What was a technical challenge that you faced as a group?
CSS ! Product stock
What was a team/personal challenge that you faced as a group?
Yaz was busy with protests at the beginning of the project, so there was some scramble after the weekend to bring everything together. Working remotely was a challenge. We're all tired from this week.
What was your application's ERD? (upload this to Google Drive, change the share settings to viewable by everyone with a link, and include a link)
https://drive.google.com/file/d/1yxRVHb_nX2m08djKieTFWYiQuD0Ulzbn/view?usp=sharing
What is your Trello URL?
https://video-store-api.atlassian.net/secure/RapidBoard.jspa?rapidView=2&projectKey=BTS&selectedIssue=BTS-2
What is the Heroku URL of your deployed application?
http://cope-and-hope-app.herokuapp.com/

saintmedusa and others added 30 commits June 16, 2020 01:03
…he model for changing cancelled status as well as other status error checking in order model
…lationship

Products categories relationship
…more thorough testing of flash to controller tests
changed product model test to reflect changes to active field, added …
end
end

describe "order" do

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You don't seem to have a nominal case here where the merchant browses orders and filters by status.

return true
end

def self.filter_status(order_items, status)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This method never seems to get called


private

def change_items(change)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you run into any validations here, you should then rollback all the other submissions.


def submit_order
@order.submit_order
if filter_cc && @order.update(order_params)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If the validation fails here, you need to rollback all the order_item changes!

@@ -0,0 +1,92 @@
class ProductsController < ApplicationController

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You should have a filter here that requires The logged in person to be the owner before letting them edit, or delete products!

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

Successfully merging this pull request may close these issues.

5 participants