This commit is contained in:
2020-01-16 20:41:24 +00:00
parent 04e6a0cad5
commit f7a8a5bcba
3 changed files with 112 additions and 60 deletions

View File

@@ -19,13 +19,10 @@ CURRENT MASTER PLAN IN CLIENT TODO
REALLY MAKING MORE PROGRESS WHEN CLIENT DEV DRIVES BACKEND DEV, STICK TO THAT!!
-----------------------
FULL format list
- What field is clickable to open??
- In a narrow list the single column is clickable but in a full list the user could have removed the "name" for example, so how does the grid handle that?
- Should the whole list return a default object type? And where would the ID value be then?
- Should all lists have an DefaultAyaType and DefaultID property separate in each row for opening?
- Or all lists have an ID column added automatically that is hidden at the client or sortable or filterable but opens the record
TODO: return the list as objects as specified
TODO: Make a joined table list for development
- User list with their email address, just name and address and user ID is enough to develop the backend code
CLIENT CUSTOM FIELDS CHANGE
- Must use numeric instead of text values now
@@ -49,6 +46,8 @@ GRID LISTS TODO NOW:
- Mock return objects for now with the new fields to include in the response see core-main-grids.txt and core-display-format-template-system.txt
DO CLIENT STUFF NOW COME BACK TO THIS STUFF LATER
TODO: the license being logged breaks the format of the log file because it has line breaks etc, so instead, maybe log out as a single line (remove breaks)