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

Extension Project + Search Bar Functionality (React)

react, styled-components
Mohsen Deniku•190
@MohsenDeniku
A solution to the Browser extension manager UI 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 could achieve almost all the objectives, and added a search bar for better user-experience.

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

Keeping the entire screen on dark mode without causing problems for other states, removing the item from the copy of the data-base, trying to find the concise way and avoiding repetition. also with the added search bar it made the entire project more intricate for me I tried to keep the filters on for the search for instance if the filter is on only active extensions and the user tries to search through using search bar only the active extensions would appear (This filter is changeable immediately using the filter buttons), this part was the most challenging part for me.

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

I still haven't managed to keep the removed item absence from the clone data and that the data becomes refreshed again after the usage of search bar, even tho I'm using useRef in order to keep track of the data and map over it. (I believe with using a real data-base where I could delete the items permanently, there wouldn't be a problem like this) I want some help with the functionality of the search bar where I can delete the project and it would re-appear after the search happens (I'm already using useRef in-order to keep track of the copy of the main data that I use to iterate over)

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Mohsen Deniku's solution.

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.