jakeheft / crate Goto Github PK

Create migration to add style column to users table

As a user, when I subscribe to a crate, that crate only lives in my subscriptions and is no longer selectable in the '/crates' page.

• This will make is so you cannot subscribe to the same crate multiple times

As a developer I want to check that the props used in each component are what I expected them to be.

Remove MySQL from package.json, since we are using PostgreSQL.

Documentation related to FE should be accurate.

As a developer I need to create a style survey component for first time users to select their style preferences.

Action: Users adds a style preference by selecting an image.

• Should be a gallery view broken up with clear product categories and instructions to "select one"
• Should select from options (will either be men or women depending on the crate they select)
• Should load product images for selection on to page
• Should be able to submit survey
• On submit FE will send survey results to BE
• BE will respond with a style summary
• FE will display that summary to the User

As a developer I want to make sure that the correct images load with the crate that was selected.

As a developer I would like to ensure my style-survey is full tested for:

All UI elements render to the screen
Conditional elements are or are NOT rendered appropriately
Submission events do occur
Post-submission messaging renders to screen
Errors are handled as expected

When a user registers, its role will default to USER.

As as a user upon completion of the style survey I would like to know that my survey was successfully submitted and get a message that communicates my results.

As a developer I'd like this to be a modal and take the users to their subscriptions page.

As a User,
When I click on + subscribe for the first time then I should be redirected to '/style-preferences' and not '/subscriptions'.

As a developer,

• Create new Route in routes folder to render StylePreferences component with the path '/style-preferences'
• Update the routing in Item.js to '/style-preferences'
• Test it to make sure it's working

As a FE dev,
I should be able to post the surveyResults data then I should receive the style in the response and display that to the user.

As a developer I would like to test my style preferences component to ensure that it performs as expected and loads the correct information dependent on the state.

All UI elements render to the screen
Conditional elements are or are NOT rendered appropriately
Submission events do occur
Post-submission messaging renders to screen
Errors are handled as expected
State is updated
Router or path is correct and renders expected elements

Make sure servers can be started for both web and api and that the application connects to the proper database.

• Bryce
• Curtis
• Estelle
• Jake
• Phil

As a user, when I am taken to '/style_preferences', I am presented with a style survey that consists of categories such as tops, bottoms, shoes, etc. I can click on the categories I like.

Set up a test suite to test features we build

• Bryce
• Curtis
• Estelle
• Jake
• Phil

As a user,
On the survey:

• clearly shows which image i have selected
• images are centered
• modal is displaying the correct style and button to subscriptions

As a developer I would like to add a style preference component to hold/render my style survey component.
This would make it easy to render conditionally if dependent on the state.

• First time user: Style-survey
• Return user: Revisit style summary and see select products with prompt to retake survey
• Troll user: style-survey with no or partial selections prompts error handling and non-submission

Images used for the Style Survey will live on the FE.

• FE team needs to add images that correspond with the survey to the public/images folder.
• Create a new folder within images to hold survey-images
• Then each style survey should have these images imported and displayed to the user.

As a user, the first time I click on '+ subscribe', I am taken to '/style_preferences'

As a user, once I have selected the categories I like, I am presented with several images from each category with instructions to choose the images that best reflects my style.

• Each image will need a style attached to it
• Add style column to user table?

BE documentation should be accurate.

Component that handles creating each "style card" (the image of clothing that user can click on)

As a team member,

I should be able to:

• Run localhost/3000 (web)
• Run localhost/8000 (api)
• Interact with the site
• Interact with the code

As a user, once I've selected images that match my style, I am given a summary of my style such as 'classic but edgy'.

• Put styles into complementary and conflicting categories (i.e. conflicting categories would yield 'classic but edgy', while complementary would yield 'classic and modern', for example)

FE team will need to put together a wireframe for how the page should look / render and how the user should be able to interact with it.