Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Devjobs web app solution | by MV

react, react-router, sass/scss, vite, typescript
P
Marcos Valenzuela•710
@Dantalian5
A solution to the Devjobs web app challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This is my first React-Typescript project, and it was quite an interesting journey filled with lots of new learning opportunities. It took some time to get everything in place.

Weak Points:

  • The use of react-router in this specific case was a bit confusing when navigating through the page, which made me doubt whether it was the right solution or not.
  • Using TypeScript made many things easier and eliminated a lot of potential errors along the way, but I realize that the indiscriminate use of 'any' wasn't the best choice in some cases, and in others, the type declarations could perhaps be improved.
  • After analyzing more advanced projects from others, I could see that maybe a more appropriate organization of the project structure and components in general could have been applied.

Despite everything, it was a lot of fun, as always. I look forward to your advice and feedback, and thank you in advance ;) .

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • BrunoMoleta•700
    @brunomoleta
    Posted about 1 year ago

    Buona sera Marcos,

    I've reviewed this project of yours also with a PR and everything. First, do not feel obliged to accept the pull request.
    Unfortunately, I ended up breaking the filter feature :(.

    I wanted to clean up the action prop that was hard to understand.

    And I know it's unnecessary to have that, though I couldn't go around it. But please check out the Git commits, as I made an effort to make each as specific as possible.

    The main thing I did was to organize the states using Zustand state manager. Also, your Button component had a reserved word "type" at your prop. I changed the name to isLink with the boolean type since it is a link or not.

    Please also check the initial color setter function. I believe it got cleaner.

    The feat you did at filtering the form as the user types is swell. Congratulations on developing it.

    Best regards from Brasile, Bruno

    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