You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
yes, we need to show what filter options on the left sidebar of the search results page
each of these options should be for a type of item, and will filter our results to only show needs
Describe the solution you'd like
A clear and concise description of what you want to happen.
a new module with a relationship to the assets table
volunteer type assets cannot have these categories (maybe add a constraint)
this is a separate table from the "interests"/"categories"/"initiatives" table (naming still TBD) that relates to users, orgs
The text was updated successfully, but these errors were encountered:
is there a reason not to just set the category name directly on the assets table? or have an enum of categories defined in the codebase?
@skyfox93 because we want, i think, a many-to-one relationship. assets can have many categories
but we actually ended up trying out single column of jsonb (so we're storing an array of the category strings)
see #296
Is your feature request related to a problem? Please describe.
yes, we need to show what filter options on the left sidebar of the search results page
each of these options should be for a type of item, and will filter our results to only show needs
Describe the solution you'd like
A clear and concise description of what you want to happen.
a new module with a relationship to the assets table
volunteer type assets cannot have these categories (maybe add a constraint)
this is a separate table from the "interests"/"categories"/"initiatives" table (naming still TBD) that relates to users, orgs
The text was updated successfully, but these errors were encountered: