From 548f075ec6db84afa6879e8b208b21afbecbef4e Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Tue, 11 Feb 2020 20:48:18 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 19 ++++++++----------- 1 file changed, 8 insertions(+), 11 deletions(-) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index 0396939f..7ddf893e 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -45,8 +45,9 @@ CURRENT TODOs SHELL / NAV / MENUS / LAYOUT - Best way to handle filters at client - - Client sends filter and sort as json fragments when requesting list - - OPEN QUESTION: Are filter and sort different fragments? + - Client sends filter and sort as json fragment when requesting list, same format as with datafilter + - Example filter and sort: + - "{"data":{"id":1,"concurrencyToken":7169684,"userId":1,"name":"SortByFieldAscendingWorks 1581453714634 1581453715083","public":true,"listKey":"TestWidgetDataList","filter":"[ { "fld": "widgetname", "op": "%-", "value": "SortByFieldAscendingWorks 1581453714634" }]","sort":"[ { "fld": "widgetstartdate", "dir": "+" }]"}}" - Saved filters are only for the client consumption not the server ever - User creates saves and selects filters at client with list type above list in ui - Relative tokens are stored in the filter as tokens, user never needs to set dates for them as they are all relative anyway @@ -57,19 +58,15 @@ SHELL / NAV / MENUS / LAYOUT - TOOD: - SERVER: Keep data filter routes and stuff at server pretty much as is but keep in mind they are only for the client's consumption - - SERVER: DataList fetcher ListOptions no longer uses datafilterid anymore nor does any part of datalist code, instead they accept a sort and filter json fragment(s) + - SERVER: needs relative date tokens back again but simply for validation to ensure they are correct tokens when storing a datafilter + - SERVER: DataList fetcher ListOptions no longer uses datafilterid anymore nor does any part of datalist code, instead they accept a single sort and filter json fragment - SERVER: DataList controller get list route change from GET to POST - SERVER: DataList controller get list route change from query string properties for listoptions to POST in FORM options (since much bigger) - - SERVER: DATALIST BIZ now must pass json frags to querybuilders + - SERVER: DATALIST BIZ now must pass json filter sort frag to querybuilders + - INTEGRATION TESTS: Update to work with new method for datafilter + - CLIENT: needs datafilter rehydration code also maybe part of doing the datafilter UI stuff - - - Filter: "{[today]}"; - - Maybe same as before however the client will update the - - Modify datalist server code to alternatively accept a json filter string instead of a filter ID (post?) - - Actually, this is jsut for relative dates so, instead how about optional start and stop date parameters to go with filterid that contains relative filter? - - Mayve need to actually make the filter client code and that will trigger the right design? - TODO: FILTER UI - Show current filter summary or text name of filter at top of filter - going to need filter name and also a summarized fragment of text showing criteria for reporting so also could purpose that list to show current filter?