-
Notifications
You must be signed in to change notification settings - Fork 1
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.
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
Add generic filter that allows user to choose which property is filtered #130
Conversation
Conflicts: src/client/components/ParticipantListPage/containers/QuickFilterContainer.jsx
export function getGenericPropertyFilterContainer(searchFilterStore, searchFilterActions) { | ||
const PropertyFilterContainer = getPropertyFilterContainer(searchFilterStore, searchFilterActions); | ||
|
||
const properties = [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Onko joku syy miksei tää oo vain objekti, kun nää on nimi-arvopareja?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Koska sekä nimeä että arvoa käytetään? Voishan ne muuttaa objekteiksi, mutta ei se mun mielestä helpota mitään...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Se ois ehkä snadisti tyylikkäämpää mun mielestä, nää arrayt joissa on array sisällä on mun mielestä vähemmän dokumentoivia. Tämmönen rakenne on perusteltu sillon kun halutaan tietty järjestys, jos se on tarkoitus niin sitä tää on tosi hyvä näin :)
|
||
} | ||
|
||
onValueChange(e) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tän vois poistaa
Muutama pikkusäätö, muutoin 5/5 :) |
No description provided.