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
2020-02-11 21:57:31 +00:00
parent 548f075ec6
commit c358cee147
1 changed files with 2 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
ayanova/devdocs/todo.txt
View File

@@ -53,10 +53,11 @@ SHELL / NAV / MENUS / LAYOUT
- Relative tokens are stored in the filter as tokens, user never needs to set dates for them as they are all relative anyway - Relative tokens are stored in the filter as tokens, user never needs to set dates for them as they are all relative anyway
- -
- If filter selected then it builds the json fragment to send based on the filter currently selected and sends that with the datalist request - If filter selected then it builds the json fragment to send based on the filter currently selected and sends that with the datalist request
- If relative dates are in it then they are rehydrated into utc iso-8601 format dates - If relative dates are in it then they are rehydrated into utc iso-8601 dates as a *BETWEEN* type filter
- Server validates filter and sort json fragment during query build, if not ok then either attempts to workaround or balks with error (probably balks is the better choice) - Server validates filter and sort json fragment during query build, if not ok then either attempts to workaround or balks with error (probably balks is the better choice)
- TOOD: - TOOD:
- SERVER: is leaking implementation details in field enum type ("enumType": "AyaNova.Biz.UserType",), modify datalist definitions to trim enum type to rightmost
- 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: 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: needs relative date tokens back again but simply for validation to ensure they are correct tokens when storing a datafilter - 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 fetcher ListOptions no longer uses datafilterid anymore nor does any part of datalist code, instead they accept a single sort and filter json fragment