This commit is contained in:
@@ -22,7 +22,7 @@ How it works:
|
||||
Unfiltered columns have a duller looking filter icon (clickable)
|
||||
Sort icon
|
||||
uses built in v-data-table sort and sort order icon system
|
||||
|
||||
|
||||
ColumnView UI
|
||||
UI opens up to same type of form as current ay-data-list-view but with only the columns visibility and order settable, no need for names it's user default
|
||||
after changes just saves as users sole default for that listkey,userid combo easy peasy
|
||||
@@ -58,7 +58,17 @@ How it works:
|
||||
REFRESH OF DATATABLE PAGE
|
||||
full page refresh / reload causes reset to default filter which triggers the fetch of the data which fills the local collection and sets teh ui for filter sort
|
||||
|
||||
UI
|
||||
V7 ISSUES FUCKERY AVOIDANCE
|
||||
ISSUES:
|
||||
Byzantine code in v7 the issues with the grid were the byzantine code behind when having to work with so many grid controls, no one control so easier off the bat
|
||||
bad filter causing issues with query, errors, timeouts
|
||||
Solution: server vets the filter and tries to ensure it is sensible so a filter on a nonexistant column should just remove the filter or whatever
|
||||
SOLUTION
|
||||
Basically make validation code have teeth at server; server only ever uses a saved filter so as long as it is saved in correct manner then it's ok
|
||||
if DataList definition updates / changes then server can easily rip through all existing filtes for that table and fixup as necessary by removing no longer columns or renaming if necessary
|
||||
|
||||
|
||||
|
||||
|
||||
LISTVIEW REPLACEMENT
|
||||
columns and sort are a singleton per datalistkey,userid persisted automatically (no alternative "views" just one of these). User can set them or reset them to default.
|
||||
|
||||
Reference in New Issue
Block a user