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

Responsive bar chart component with JSON data fetching

sass/scss, bem
Elaine•11,360
@elaineleung
A solution to the Expenses chart component challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Just updated my solution as I realized that I had mistaken the highlighted bar to be the day with the largest amount, when in fact it should be the current day (as in, in real life). I also made the component responsive even at smaller sizes instead of just having two fixed widths; this normally is not so hard to do since content tend to be filling up the container, but in this content here is smaller than the container. To make sure the container doesn't collapse, I used the responsiveness of flex-wrap to ensure it would be at the size I need.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Amaefula Joel•470
    @Amaefula-Joel
    Posted about 3 years ago

    I'm really interested in knowing how you make your solution match almost identically to the design. What app do use? If it isn't an app, how do you make the perfect comparison

  • Renan Tiscoski•1,240
    @DonUggioni
    Posted about 3 years ago

    Hello Elaine,

    I have a question about your code, as I'm currently working on this solution, I need some help =D

    ${info.amount * 0.1595}em => how did you arrive at this value? The one you are multiplying the info amount by.

    Curious about how you got there!

    Thank you =)

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

Oops! 😬

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

Log in with GitHub