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

Password Generator app responsive

P
JeronimoCardu•580
@JeronimoCardu
A solution to the Password generator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Brian Meinert•380
    @bmeinert8
    Posted 2 months ago

    Good work on your project the password generation works well along with the strength detection. A couple suggestions for you if you'd like to go in and implement them in your project:

    1. Strength detection: The strength detection works as intended displaying the strength and filling in the bars. One thing you could do to enhance it would be to add a logic check to it by creating a function that would not only take into account not only the type of characters in the password, but also the length of the password. For example
    function updateStrength(charTypes, passwordLength) {
      let passwordStrength = '';
      let strengthLevel = 0;
    
      if (charTypes === 4 || (charTypes === 3 && passwordLength >= 12)) {
        passwordStrength = 'Strong';
        strengthLevel = 4;
      } else if ((charTypes === 3 && passwordLength >=8) || (charTypes === 2 && passwordLength >= 10)) {
        passwordStrength = 'Medium';
        strengthLevel = 3;
      } else if ((charTypes === 2 && passwordLength < 10) || (charTypes === 3 && passwordLength < 8)) {
        passwordStrength = 'Weak';
        strengthLevel = 2;
      } else if (charTypes < 2) {
        passwordStrength = 'Too Week!';
        strengthLevel = 1;
      }
    
    1. Copy button: I struggled with getting the copy button to copy the generated password to the clipboard myself but after some research and trial and error I was able to get it working using the clipboard API

    Overall great work and keep it up!

    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