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

Interactive card details form using React & Sass

react, sass/scss, vite
vietan0•430
@vietan0
A solution to the Interactive card details form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Some concerns I have after finishing this project:

  • In the Sass file, am I nesting rules too deep?
  • Is my code in validate.js easy to comprehend?
  • What would you do to improve the "injecting spaces every 4 digits" part? Also any tips in how I wrote React in general is welcomed. I've been learning on my own and not quite sure how readable my React code is.
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • David•7,960
    @DavidMorgade
    Posted almost 3 years ago

    Hello Vietano, congrats on finishing the challenge!

    I will try to answer your questions and give you my personal opinion on your code:

    • I think yes, 4 nested CSS selectors are hard to read, you should stick to maximum 3 to make your code more readable and easy to change / understand, try maybe using BEM to avoid excesive nesting or just call the class in another block on your SCSS.

    • Well I can understand it, but it can be more easy to read if you change a bit your habits of your Javascript style, but this can be a hard path and it will just come with time, for example:

    Instead of for of loop (wich yes, they run faster but are way less readable), use array methods like map(), forEach() etc... instead of using if else checks try using ternary operators or logical && || operators, this are modern features that can reduce your code a lot and make it more readable. Dunno how exactly Vite works, since I have only used Create react app and NextJS but you should divide your project in a lot of components, instead of having everything on one file.

    • As I said before I think using Array methods here could have done the job easily for you.

    Hope my feedback helps you, if you have any questions don't hesitate to ask, you did a great job, welcome to the react community of frontendmentor!

    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

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