Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 2 years ago

Connect-Four

react, react-router
AlexBetita•60
@AlexBetita
A solution to the Connect Four game challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This was one fun and quite challenging. Added ESC key functionality on the game board component for pausing the game. Added error handlers for wrong routes.

Didn't make it as responsive only followed the 3 dimensions that figma provided. Desktop 1440x900 Tablet 768x1024 Mobile 375x812

Difficulties:

  • Coding out the game logic.
  • Naming conventions for CSS class names.
  • Had an issue with my event listener causing lag on each rerender, found a fix with the use of useCallback. I needed to memoize the event listener.
  • Creating the pause menu with a timer, had to have the timer pause as well.
  • Creating a mobile friendly and tablet version.
  • Practicing SRP near completion at the end I just had to get functionality working
  • States got pretty messy.
  • Creating the grid layout and designing the grid layout.

Areas of unsureness.

  • proper values for height and width of divs.
  • the use of divs for almost everything.
  • the use of CSS, majority of the elements had static values. Not sure how to improve on that area.

Best practice?

  • How I did my components, not sure if that is the right way to go.
  • My states were all over the place.
  • I had to prop drill a restart function down to a child component and have that child pass in its setState functions into the function in order for all the states to be accessed by one component. It was a beautiful mess of a code.

Extra: Wanted to added local storage caching when an ongoing game is happening if a user decides to refresh or accidentally refreshes the page. But due to how convoluted my states where I decided not too xD.

Also was gonna add a computer player as one of the bonuses. But Id rather just work on another challenge.

Shout out to visauldennis for the feedback on my last solution. Rem is a pretty useful value for font sizes and I added visual clarity when hovering over buttons.

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 AlexBetita'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
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.