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

Vanilla JS & SASS

sass/scss
P
Nate Valline•420
@nvalline
A solution to the Password generator app 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 feel like I was able to work through the JS logic pretty easily to get this app to function properly.

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

The biggest challenge was to get the checkbox styled to the design specs. But that in my opinion was a fairly small challenge.

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

I would appreciate any tips/suggestions on how to improve my code. Thanks!

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Julien Gilbert•500
    @juliengDev
    Posted 8 months ago

    Hello again @nvalline :)

    Here are the points I liked compared to my own approach:

    •	Use of crypto.getRandomValues: This is a good practice to enhance the security of the password generation process.
    •	Validation of options: The logic for validating options using FormData is interesting to ensure that at least one option is selected before generating the password. This could be useful if I want to implement more rigorous validation in my own code.
    •	Visual feedback on the slider: The visual feedback on the slider’s progression is a nice enhancement for the user interface and could be a good addition to my project.
    

    The design is faithful to the original mockup, and I'm always impressed by how you're able to achieve an almost pixel-perfect integration.

    I noticed an issue in the application where, if you adjust the slider to set a maximum number of characters but don’t check any options, the output displays undefinedundefinedundefinedundefined. Perhaps you could add a validation step in the logic to handle this case.

    Congratulations on the code and the project! Keep up the 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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

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

Log in with GitHub