Closed feeds closed 3 years ago
I agreed with @maltezacharias that this should be merged as it is a useful mockup that will obtain nicer UI elements in the future, so it is useful to merge this into staging
I don't understand all these filter PRs. @feeds Is this description still up-to-date?
Create a new Filter that is saved in http://127.0.0.1:8000/matching/A/filter/create or call the rest api to filter the existing participants with get parameters http://127.0.0.1:8000/matching/api/A/info/list (see OPTIONs-button)
Sorry, the added user functions are
go to dashboard as a participant you have two new options: search for opposite participants and view past searches
search: filter possiblity on top that will be replaced by a js filter layout, table that shows results below that will also be replaced by a js component that makes calls to an api route that already exists in this PR api/A/info/list
. One can then select several participants with a checkbox. Then a popup opens to promt subject and message. On send the filter is saved and the contacted people are put in a database. Return to dashboard.
saved search: list of searches that were already made. Shows how many matches exists in the database live. later should show how many of those were contacted, button for search again, Button for contact all i did not contact before.
db changes :
name
, contact
and phone number
exist when http://127.0.0.1:8000/matching/A/filter/create/ also allows me to search for boolean etc. fields?name
- [ ] Is it on purpose that only search fields for
name
,contact
andphone number
exist when http://127.0.0.1:8000/matching/A/filter/create/ also allows me to search for boolean etc. fields?- [ ] No possibility to name the filter but http://localhost:8000/matching/B/filter/list/ includes
name
- [ ] No description:
- [ ] I can search for letters in the phone number
The UI is only a mockup, we are working on an endpoint that provides the available filters to the Javascript side and an UI that dynamically builds on this
@maltezacharias Then please migrate the points which you are working on to the corresponding issue. It's hard to review without knowing what the intended functionality is and, even more important, not knowing which functionality is not intended for this PR.
@feeds and me opened #176 and #177
Now also fixes #176
Allows to
I still need some input on what people should actually see in the filter - right now its not pretty
Also we would need to figure out the logic behind what sort of matches new ones are. @Baschdl
Also fixes #176
oops
You can use the persistent filters from a participants dashboard
Fixes #176 Closes #37