Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Original with React TypeScript Tailwind

preact, typescript, tailwind-css
Mahdi Karimian•610
@Mahdii-Kariimiian
A solution to the Rock, Paper, Scissors game challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

This project is a Rock-Paper-Scissors game built with React , Typescript and Tailwind Css. The game features the following components and functionalities:

Components:
    Hero: The main component that houses the game logic and state management.
    Score: Displays the current score of the player.
    Icons: Represents the selectable icons for rock, paper, and scissors.
    Rules: Shows the game rules in a modal.
    Winner: Displays the result of the game round, indicating whether the player won, lost, or drew.

State Management:
    Score: Keeps track of the player's score.
    isRulesOpen: Boolean state to control the visibility of the rules modal.
    myChoice: The player's choice (rock, paper, or scissors).
    computersChoice: The computer's random choice.
    winner: Indicates the result of the game round (You, The House, Draw, or null).

Game Logic:
    Icon Selection: The player selects an icon, triggering the computer's random choice after a brief delay.
    Determining the Winner: The winner is determined based on the rules of Rock-Paper-Scissors. The game checks combinations to see if the player wins, loses, or if it is a draw.
    Score Update: The score is updated based on the result of the game round.

User Interface:
    Before Choice: The player is presented with three icons (rock, paper, scissors) to choose from.
    After Choice: Displays the player's choice, the computer's choice, and the result of the game round.
    Rules Modal: Displays the rules of the game when the rules button is clicked.

Styling:
    The project uses Tailwind CSS for styling the components, ensuring a responsive and visually appealing interface.
What challenges did you encounter, and how did you overcome them?

Writing the correct Type for every variable in Typescript.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Mahdi Karimian's solution.

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.