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

Solution that waits for new quotes

P
Grog the Frog•480
@GregLyons
A solution to the Advice generator app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I tried to implement a feature where the button will be disabled for 2 seconds after fetching (since that's how the Advice Slip API works; it returns a cached version of the previous quote if you request too frequently). It seems to work decently, but I've noticed that rapidly clicking on it can break it. Is this something you run into, and if so, how would you handle it?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Luis Castillo•380
    @lipe11
    Posted about 3 years ago

    hi,

    I think the timeout worked pretty good. I tried to fast click the button but barely saw it act weirdly.

    However, if you want to get rid of the effect, you might want to try something like throttling. I'll leave a reference here. As a first approach, you could try something like this

    let waiting = false
    
    buttonWrapper.addEventListener("click", (e) => {
      if (waiting) return
      waiting = true
      getAdvice()
      setTimeout(() => {
        waiting = false
      }, 2000);
    })
    
    Marked as helpful
  • Ivan•2,610
    @isprutfromua
    Posted about 3 years ago

    also i found some css issues: use only one type of selectors (class or id, but class is preferred)

    .card__text {
    
     ....
    #card-button {
    

    it's better to set class for an image

    #advice-button > img {
      display: block;
    }
    

    it's not good to use nesting selectors with bem methodology

    .card__wrapper > .card__header {
    
    Marked as helpful
  • Ivan•2,610
    @isprutfromua
    Posted about 3 years ago

    Hi there. You did a good job 😎

    🛠️

    keep improving your programming skills

    your solution looks great, however, if you want to improve it, you can follow these steps:

    ✅ you can do it with HTML picture

    function changeDivider() {
      const dividerImg = document.getElementById('divider-img');
    
      if (window.innerWidth > 500) {
        dividerImg.src = 'images/pattern-divider-desktop.svg';
      }
      else {
        dividerImg.src = 'images/pattern-divider-mobile.svg';
      }
    }
    

    ✅ there is no need to prevent event inside the fetching function

    getAdvice(e) {
      e.preventDefault();
    
    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

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