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

GitHub user search using React and MUI

react, material-ui
Matt Seidel•570
@mseidel819
A solution to the GitHub user search app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


The links section at the bottom doesn't look great with long urls. Any suggestions on how to tighten that up?

When there is no user found, what should I display in the profile container?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Vanza Setia•27,715
    @vanzasetia
    Posted almost 3 years ago

    Hi, Matt Seidel! 👋

    Good effort on this challenge! 👍

    Regarding the long URL, I also experienced the same thing. I suggest reading my README where I explain the issue and how to solve the issue. But, to give your an overview of the answer, you can use some CSS properties to solve the issue (text-overflow, overflow, and white-space).

    If the user doesn't exist then I would recommend only showing the "No results" message without wiping out the content inside the container. I can't give you a guide on how to do it since I am not a React developer. 😅

    One small suggestion I have is to fix the issues that have been reported by Frontend Mentor. Also, one bug that I noticed in your app is that I have to click the search button to search the user. I can't just use the Enter key to search for a user. It might be because the input and the search button is not wrapped by the form element.

    That's it! I hope this helps! 🙂

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