Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 3 years ago

Tic-Tac-Toe made with React, Redux Toolkit, and Sass

react, redux, redux-toolkit, sass/scss
Bradley Wright•80
@rapidswing
A solution to the Tic Tac Toe game challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hello! Besides general comments and bug reports...

  • are there any React best practices or patterns I should look into?

  • my Redux game slice feels chunky, should I split it up?

  • any browser specific CSS/Sass styling errors?

Thanks!

Notes:

  • clicking the XO logo on either screen will access the difficulty settings

  • the modal is slightly transparent for game results to be visible through it

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Roman Zvir•290
    @rmzvr
    Posted over 3 years ago

    Wow, great job, the code is well destructured, I like your writing style, I don't have enough redux knowledge to give hints yet. This project was next in my plans, maybe I will peep at your decision as inspiration)

    The only thing I noticed was hovering over the buttons on the welcome screen: When hovering over the side select buttons, the pointer appears on the X and O icons themselves, and not on the entire button. When hovering over the buttons, there is also no new game pointer, it is not visually clear whether these buttons are active.

    Marked as helpful

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
Frontend Mentor logo

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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

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

Log in with GitHub