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

Job listing with Vanilla JS, still stuck with filter functions

Duyen Nguyen•950
@Duyen-codes
A solution to the Job listings with filtering challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


My filter function is not finished. I'll do more research and continue working on finishing the challenge later. I'm doing this with JS with no library or framework. I'd really appreciate if you could look at my codes and give me some lead of how to move forward with the functions. Any help/ feedback is greatly appreciated. Thanks!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Gürkan Özer•420
    @gurkanozer
    Posted about 3 years ago

    Hi, Duyen. I don't know if this help but this is how i did.

    `let filterList = []

    fetch(){ //get datas

    //and create all cards

    //visible cards has class named active so in this case i added active class to all cards.

    //then select all tags in document.

    const tags = document.querySelectorAll('.tag');

    //and create event listener for each one.

    tags.foreach(tag=>{

    tag.addEventListener('click',()=>{

    //add this tag to filterList.

    //you need filter all cards by filterList. Then remove class active if card

    //dont have this tag

    });

    //and re-render cards

    }); `

    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 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