admin/raven-client
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Browse Source
This commit is contained in:
John Cardinal
2021-01-29 19:32:00 +00:00
parent 339ad105e5
commit 92ebf2ab65
1 changed files with 6 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
ayanova/devdocs/todo.txt
View File

@@ -6,8 +6,8 @@
MISC ITEMS THAT CAME UP
How it works:
user opens grid for first time this session, default filter is in effect
grid sends request to server consisting of offset, limit, datalistkey, clientCriteria and Filter id to apply or empty / 0 if wants default server filter
user opens grid for first time this session, client sets filterid to 0/default and triggers fetch of the filter list which in turn triggers getdata
GetData sends request to server consisting of offset, limit, datalistkey, clientCriteria and Filter id to apply or empty / 0 if wants default server filter
Server gets the filter specified which is either user default or anotehr named filter and is alwasy in the DataListSavedFilter table userid/listkey/default:or:filterid
server responds with same data as now which includes column order so that is handled already but new additional data:
Sort data - so client can modify datatable display to mirror upon receiving data
@@ -22,6 +22,8 @@ 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
Column order / visibility
Replace current filter icon with column order visiblity icon and just keep as is in UI of datatable (modify columnview ui as per below)
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
@@ -53,7 +55,8 @@ How it works:
on CANCEL it only closes the filter manager UI and does nothing else
on RESET it tells teh server to reset the current filter to default via RESET ROUTE , exits and triggers filter picklist to udpate itself triggering a getdata
SERVER / GETDATA
when server returns data for table it also includes the sort and filter in effect which is saved locally inside the vm data for use by filter UI (doesn't survive refresh)
when server returns data for table it also includes the sort and filter in effect which is saved locally inside the vm data for use by filter UI (doesn't survive refresh)
server applies filter id specified in request if filterid is 0/default then it fetches their default filter (which in turnr makes one if it doesn't find one)
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