Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Filter options should be read from the database #252

Open
abbiefarr opened this issue Jul 22, 2021 · 1 comment
Open

Filter options should be read from the database #252

abbiefarr opened this issue Jul 22, 2021 · 1 comment
Labels
epic: filtering Tickets related to Filtering idea Suggested feature requests validated

Comments

@abbiefarr
Copy link

We're currently hard coding options for filtering, which is brittle and not very extensible. We should somehow programmatically align filter options with database options, either by reading options from the database or using enum values.
@abbiefarr abbiefarr added the epic: filtering Tickets related to Filtering label Jul 22, 2021
@ludtkemorgan ludtkemorgan added the idea Suggested feature requests label Apr 4, 2023
@ludtkemorgan
Copy link
Collaborator

Notes:

  • This is referencing the frontend is hard coding the same values that exist on the backend. we should use the same enums in both places.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
epic: filtering Tickets related to Filtering idea Suggested feature requests validated
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ludtkemorgan @abbiefarr