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

Intro component Validation form HTML/SCSS/JS

Valentin•290
@cheepmanzee
A solution to the Intro component with sign-up form challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


All feedback is highly appreciated! How can I improve validation so password and name couldn't contain symbols, foreign charcaters etc. Also, how can I change the error text with js depending on error issue? Like if there are spaces in password - show text 'Password can not contain spaces' and similar. Thanks in advance!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Siege•520
    @idesmar
    Posted over 3 years ago

    For extra validation on name, password, etc.:

    You may want to dive in on Regular Expressions.

    Here's an example on evaluating a name value if it has an invalid character

    const notAWordCharacterRE = /[^a-z]/ig;
    let nameValue = "name$";
    let invalidNameFormat = notAWordCharacterRE.test(nameValue); // result: true for "name$"
    if (invalidNameFormat) {
    // code here for adding error message
    };
    

    Additional reading: Regular expression syntax cheatsheet

    Regular Expressions or RegExp can be a bit overwhelming sometimes but it's going to be a great help moving forward.

    Always be hungry for more learning and happy coding!

  • Siege•520
    @idesmar
    Posted over 3 years ago

    Great work! Your app was responsive and passes all the project's requirement!

    On the question on custom error message, you can create a nested "if statement" or a "switch statement" that adds a more specific error message. I made a slightly similar error handling process on my project that focuses on the email. There are 2 possible error message on the email field; either empty or invalid email. Here's a link to the web app I made.

    I hope that was of help. Happy coding!

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

Oops! 😬

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

Log in with GitHub