Required Features 🎯

• User can see two of the same ChoiceCard components.

• User can see two different titles in our ChoiceCard components.

• User can see two different images in our ChoiceCard components.

• User can see two different prompts in our ChoiceCard components.

• User can see two different border colors in our ChoiceCard components.

• User can see three buttons labeled Rock, Paper, Scissors.

• User can press one of the buttons to make their choice.

• User faces a computer who also makes a choice from Rock, Paper or Scissors.

• User can see text indicating that they've won, lost, or tied.

• User can see either green/red depending on whether or not they've won.

• User can see a game history which lists the rounds played so far and outcome.

• User can only play the game once they've pressed a button titled Start.

• User can sign in and have their name attributed to the victory.

• User can see the prompt colored correctly based on the outcome of the game. If player has won, "Victory!" is green. If player has loss, "Defeat!" is red. If the result is a tie, the text remains black.

• User sees "flawless" victory behavior in the game. If the user/computer wins the first 3 rounds in a row, they've achieve a flawless victory.

This project was bootstrapped with Create React App.

Available Scripts

In the project directory, you can run:

npm start

Runs the app in the development mode.
Open http://localhost:3000 to view it in the browser.

The page will reload if you make edits.
You will also see any lint errors in the console.

npm test

Launches the test runner in the interactive watch mode.
See the section about running tests for more information.

npm run build

Builds the app for production to the build folder.
It correctly bundles React in production mode and optimizes the build for the best performance.

The build is minified and the filenames include the hashes.
Your app is ready to be deployed!

See the section about deployment for more information.

npm run eject

Note: this is a one-way operation. Once you eject, you can’t go back!

If you aren’t satisfied with the build tool and configuration choices, you can eject at any time. This command will remove the single build dependency from your project.

Instead, it will copy all the configuration files and the transitive dependencies (webpack, Babel, ESLint, etc) right into your project so you have full control over them. All of the commands except eject will still work, but they will point to the copied scripts so you can tweak them. At this point you’re on your own.

You don’t have to ever use eject. The curated feature set is suitable for small and middle deployments, and you shouldn’t feel obligated to use this feature. However we understand that this tool wouldn’t be useful if you couldn’t customize it when you are ready for it.

Learn More

You can learn more in the Create React App documentation.

To learn React, check out the React documentation.

Code Splitting

This section has moved here: https://facebook.github.io/create-react-app/docs/code-splitting

Analyzing the Bundle Size

This section has moved here: https://facebook.github.io/create-react-app/docs/analyzing-the-bundle-size

Making a Progressive Web App

This section has moved here: https://facebook.github.io/create-react-app/docs/making-a-progressive-web-app

Advanced Configuration

This section has moved here: https://facebook.github.io/create-react-app/docs/advanced-configuration

Deployment

This section has moved here: https://facebook.github.io/create-react-app/docs/deployment

npm run build fails to minify

This section has moved here: https://facebook.github.io/create-react-app/docs/troubleshooting#npm-run-build-fails-to-minify