Normalize treatment of filters on the front end

Created on 27 January 2025, 2 months ago

Problem/Motivation

The Svelte app has a few locations where it specifically checks for the hard-coded existence of certain filters, like development status, security coverage, and such. This makes it awkward for the sources to define their own filter sets -- which is something they have an API for. The frontend should respect that.

Proposed resolution

Normalize the treatment of filters; just treat them as different types of values, and don't worry about which filters are specifically defined. Each different type of filter downcasts to a particular value in a URL query string, so handle them generically.

📌 Task
Status

Active

Version

2.0

Component

Code

Created by

🇺🇸United States phenaproxima Massachusetts

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Merge Requests

Comments & Activities

  • Issue created by @phenaproxima
  • Pipeline finished with Failed
    2 months ago
    Total: 722s
    #407517
  • Pipeline finished with Failed
    2 months ago
    Total: 462s
    #407547
  • Pipeline finished with Failed
    2 months ago
    Total: 524s
    #407553
  • Pipeline finished with Failed
    2 months ago
    Total: 378s
    #407562
  • Pipeline finished with Failed
    2 months ago
    Total: 457s
    #407570
  • 🇺🇸United States phenaproxima Massachusetts

    One ESLint failure that seems like bullshit to me; I'm not sure how to fix it without breaking the test.

    Otherwise this is good to go. Filtering has been a real mess in Project Browser for a while, and this doesn't take us all the way to where we need to go, but it's a big step forward.

  • First commit to issue fork.
  • Pipeline finished with Success
    2 months ago
    Total: 817s
    #407632
  • 🇮🇪Ireland lostcarpark

    Fixed the ESLint issue. Everything is green now.

  • Pipeline finished with Failed
    2 months ago
    Total: 231s
    #407662
  • Pipeline finished with Canceled
    2 months ago
    Total: 89s
    #407666
  • Pipeline finished with Canceled
    2 months ago
    Total: 88s
    #407667
  • Pipeline finished with Success
    2 months ago
    Total: 357s
    #407668
  • Pipeline finished with Skipped
    2 months ago
    #407690
  • First commit to issue fork.
  • 🇺🇸United States chrisfromredfin Portland, Maine

    Another great diffstat AND I really did a ton of manual testing. This is such a great unblocker for future source plugins.

  • Automatically closed - issue fixed for 2 weeks with no activity.

  • Pipeline finished with Failed
    about 2 months ago
    Total: 1290s
    #430515
  • Pipeline finished with Canceled
    about 1 month ago
    #430595
  • Pipeline finished with Failed
    about 1 month ago
    Total: 1215s
    #430601
  • Pipeline finished with Failed
    about 1 month ago
    Total: 803s
    #430627
  • Pipeline finished with Failed
    about 1 month ago
    Total: 1222s
    #430636
  • Pipeline finished with Canceled
    about 1 month ago
    Total: 629s
    #432877
  • Pipeline finished with Success
    about 1 month ago
    Total: 1235s
    #432882
  • Pipeline finished with Failed
    about 1 month ago
    Total: 1099s
    #433377
  • Pipeline finished with Success
    about 1 month ago
    Total: 7160s
    #433483
  • Pipeline finished with Failed
    about 1 month ago
    Total: 1224s
    #434622
  • Pipeline finished with Success
    about 1 month ago
    Total: 1299s
    #434716
  • Pipeline finished with Canceled
    about 1 month ago
    Total: 110s
    #434756
  • Pipeline finished with Canceled
    about 1 month ago
    Total: 138s
    #434757
  • Pipeline finished with Success
    about 1 month ago
    Total: 1331s
    #434760
Production build 0.71.5 2024