rrabinovitch / crate Goto Github PK

• The user's style will display persist above their subscriptions.

Ensure that once new style is saved to a user and null is replaced, fe has access to that style and can display it

• If all categories selected, user can submit their style type
• If a category is missing, user cannot submit their style type and receives a warning message of what is missing

Feature:
Before adding a monthly subscription I would like to choose my style preferences to ensure that I get clothes that better match my personal style. When I visit /crates, the first time I click on + subscribe I am taken to a style preferences page /style-preferences. I am presented with a style survey that consists of a series of categories such as tops, bottoms, dresses, shoes, accessories, etc. For each category I am given several images to choose from with instructions to choose the images that best reflects my style. After I have chosen the images from each category I am given a summary of my style such as ‘classic but edgy’.

Extensions:

• When I visit my profile page, I can see a button to view my style survey. When I click on the button, I am taken to /style-prefences and can edit my style preferences to update my style at any time.

• I would like to fill out a style survey for different categories of my wardrobe i.e. work, casual, date night. For each category I am presented with the same categories of choices i.e. tops, bottoms, dresses, shoes, accessories, etc.

• Update the user state file to have a style property.

As each of us collects images for our assigned profile and categories, add the links to this slack thread.

Style profiles/types:

• posh - @H-Bo214
• scary - @tarynmartin
• baby - @rrabinovitch
• sporty - @Ashkanthegreat
• ginger - @NickEdwin

Categories: each style type has an image for each of the following categories

• tops
• bottoms
• shoes
• accessories

To be included:

• Reference comments from repo setup card #3
• ERD #9
• user flow, wireframes, and data flow #10 #11

We'll get together to discuss and map out the user flow on jamboard or miro

When FE provides an array of numbers generated by a user's style preferences selection and the user's id,
BE logic calculates the most frequent number in the array in order to identify the user's style preference label (ie, sporty, posh, scary, etc.).
A User model mutation updates the user style column with the identified style preference.

Implementation details:

• make conditional logic work one way or another - doesn't matter exactly where it lives (issue #30 will refactor as needed)
• create a mutation
• FE to provide which style is associated with which number that is being passed into the array @tarynmartin @H-Bo214

Style survey track info here

Check the box next to your name when you've completed this item:

• Ruthie
• Nick
• Horacio
• Taryn
• Ash

User can select one item in each category (tops, bottoms, etc)
Once a user has selected on item in each category, they click on the submit button and receive a message with their style type

When a user logs in, they are taken to the crate subscription page.
On clicking + subscription on a crate, if no style saved to user, it automatically takes them to the style survey page

Switch from using seeded data to instances created within test file for User query test & add server closing code

When a user submits their info, BE uses API to manipulate the information before passing it onto the database & adding to the user's info

Implementation details:

• BE creates a User update endpoint with conditional logic to identify which style label/category to save

Resources:

• Alex's lesson

• Server Side Testing using Jest and supertest

• Server Side Testing with a DB

• Jest documentation

• Jest documentation re: setup and teardown

• stackoverflow re: Jest teardown

• Jest expectations

• supertest documentation

• Approved, but left in this column for future ref if needed.

Style Survey track info here - also see issue #2

Submission instructions

Requirements:

• Create a branch called code-annotations-yourname
• Each team member will submit their own branch
• Make a list of the specific files of code that will need to be updated in order to add the additional features outlined in your track
• For each file, walk through the code and add a comment above each line/block that describes what that code is doing.
• Submit a link to your branch here

Check the box next to your name when you've completed this item:

• Ruthie
• Nick
• Horacio
• Taryn
• Ash

Instructions here

When you're done with setup, answer the following questions in a comment below:

• what went well as you set up the application?
• what strategies did you use when running into errors?
• what things did you find helpful in the documentation?
• what notes do you want to make sure are included in the readme?

Check the box next to your name when you've completed this item:

• Ruthie
• Nick
• Horacio
• Taryn
• Ash

As a user completing my style survey,
If I select two styles an equivalent number of times,
< decide what to implement as a 'tie breaker' >

Feature:
As a user, it’s frustrating to go to my profile page and see little about myself other than my subscriptions. To give the user more control, I’d love to upload my own image, set a personal description, edit my email address and shipping address, and see a history of products that have been delivered to me and what I have kept. I should also see when my next delivery is coming and adjust the date for when I am available.

Extensions:

• As a trendsetter who values fashion, I would also like to be able to share this as a public URL (don’t have to have an account or be signed in) so that users can see my subscriptions and items that I have chosen to purchase as well. This page should include my profile picture, but keep info including my email address/shipping address, order history, and delivery times private.
• As a user, I should be able to tweet which clothes I have purchased. (actually integrate it with the Twitter API)

• Add ability to select a single item in a row (ex. tops)
• Once clicked, the user knows their item is selected
• StyleSurvey has a submit style button

currently a user is created with their style preference defaulting to undefined

change this attribute default value to null so that it is a more intentional value

Refactor #27 and identify where it makes most sense for this logic (ie, which style a user is being assigned) to go