Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 12 months ago

Qr code component, using React and styled-components

react, styled-components
TomLuizCP•10
@toni500madmax
A solution to the QR code component 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?

I have many points to improve, especially the begin the project, it's very strange and hard to think in a solution rapdly and efficiently.

What challenges did you encounter, and how did you overcome them?

I figured out that gotta to study much more styled components and prop types through it.

What specific areas of your project would you like help with?

At this time i need how to start a project, how to define architeturies of archives and other things, and where should i start for in a new project...

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Natalie Smyth•340
    @nataliesmyth
    Posted 12 months ago

    Great job, your app looks just like the design given.

    I have some suggestions from my own experience learning to program

    1. I highly recommend understanding CSS and vanilla JavaScript before trying to learn frameworks like react. JavaScript frameworks and libraries are built with vanilla JavaScript, and learning react without understanding JavaScript is like building a house with no foundation; the smallest obstacle will make the whole thing fall.
    2. Frameworks like react are unnecessary for projects using HTML and CSS without JavaScript, and implementing react here added a lot of unnecessary code. So for this project, you may be better served to focus on getting comfortable with html and css, then add JavaScript, and then later in your journey add frameworks.

    All the best! Great Work!

    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 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