From cb4a9d0f39e9b88c4524586ba99006e366192465 Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Fri, 17 Jan 2020 00:54:10 +0000 Subject: [PATCH] --- devdocs/todo.txt | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/devdocs/todo.txt b/devdocs/todo.txt index 0f377048..9f2a548c 100644 --- a/devdocs/todo.txt +++ b/devdocs/todo.txt @@ -26,6 +26,13 @@ GRID LISTS TODO NOW: - i.e. if I want to make a widget->user->Email report and a separate user email report are they each in widget and user - Or, because they are read only lists used for many things do they just go into a central route for read only lists? - Also rights issues might affect this..? + - One central route with keys would simplify the client end UI certainly + - Maybe all WidgetController routes are only for CRUD (and mass change) ops and not for list retrieval? + - Would simplify the WidgetController and biz for sure + - one central route would get pretty huge though, will be clearer once I abstract out the bits + - Maybe instead of the objectFields monolithic class I have one small class for each list and or UI editing definition that all feed into a central spot + - This way each type is in it's own file and cleaner? + - UI custom fields and shit part is kind of separate from the list stuff with only a bit of overlap, maybe they are separate objects once again and split out? - Update tests when appropriate (when it's working fully and not mocked) - 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