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

interactive-comments-section

react, styled-components, vite
Alexander Hergert•710
@alexander-hergert
A solution to the Interactive comments section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This was a funny project. Probably some refactoring would not harm the project and will be a goal in the future. I have tried to make the project a bit like the comments section on youtube or similar websites. I have tried to practise a bit useReducer and context API. My feeling is that the code feels overcomplicated still but thats going to be a target in the next future to simplify it more. For now it feels good but some critical bugs will be fixed as soon as encountered :) Feel free to check it out. You can switch users on top to simulate another log in. If you leave the comments empty then you will send a random quote. Here I had already some funny conversations lol. Make sure to expand the comment if you want to check a reply. They are closed by default.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • sambuka-a•420
    @sambuka-a
    Posted almost 2 years ago

    thanks for the reply.Now I got it) Interesting approach. It would work even better with thumbs up/thumbs down. Honestly I didn't notice + and - active (blue) state, that is why it was a bit confusing. It is a really good idea to allow only one single reaction per active user. Don't have it in my solution. I did my reaction logic something similar to stackoverflow (negative score allowed + posts are sorted depending on score). But I should also really add user vote limitation per post/comment. Good luck in your WebDev journey

  • sambuka-a•420
    @sambuka-a
    Posted almost 2 years ago

    Nice solution. Bzw, seems like post score logic doesn't work properly. In case you would like to play around fixing it

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.

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