devdocs/todo.txt

@@ -5,43 +5,34 @@ eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpYXQiOiIxNTcxODU5OTU0IiwiZXhwIjoiMTU3MjQ
 
 ## IMMEDIATE ITEMS
 
-REFACTOR OBJECT FIELDS AND DATA LISTS
-	AyaObjectFieldDefinitions is doing double duty for two completely different uses right now and needs to be split up
-	split ayaobjectfielddefinitions into two entities:
-		LISTS:
-			used for data list filter, sort template builder
-			used for building queries
-			etc
-			- AyaDataList abstract class containing
-				- AyaObjectFieldDefinitions (RENAMED to AyaDataListFieldDefinitions)
-					- Extracted from ayaobjectifielddefinitions
-				- SQL from query
-				- AyaDataList key (used by many things including the AyaDataListDisplayTemplates)
-				- LIkely rights as well maybe a down the road issue to be added later?
-		FORM FIELDS:
-			Used for form customization
-			available fields to select for show etc
-			Extracted from ayaobjectfielddefinitions
-			Essentially the same thing as it is now, so maybe just rename the existing one
 
-Make DATALIST route for fetching all keys (list object names essentially)
+Make DATALIST route for fetching all datalist key names
-Make datalist route for fetching the field list of a specific datalist by key
+Make datalist route for fetching the field list of a specific datalist by key name
+Make dataList route for fetching the actual data 
+
+
+Clean up AyaObjectField definition for FORM FIELD STUFF:
+	Used for form customization
+	available fields to select for show etc
+	Extracted from ayaobjectfielddefinitions
+	Essentially the same thing as it is now, so maybe just rename the existing one
+
 
 MAKE DATALIST ROUTE FOR FETCHING LISTS BY KEY
 	- REMOVE LISTS FROM INDIVIDUAL OBJECT ROUTES AS MUCH AS POSSIBLE
 	- Accepts datalist key
 	- finds applicable AyaDataList object for the key specified (maybe keeps a static list of them rather than finding upon reflection)
 
-GRID LISTS TODO NOW:
+
-	- Make a joined table list for development 	
+UnMock MOCK_WIDGET_DISPLAY_TEMPLATE_JSON into db with objects and with seeded data for test and or all lists
-		- Widget list with User and their email
+	- One single object with all templates in JSON maybe? since there are not going to be multiple templates for same list object anyway
-	- Make regular list of widgets with all columns no joins as second list	
+		- Server can load it up and cache it like LT?
-	- return the lists properly as objects as specified
+	- Can it just make a default template if none is found?  (no they are all required)
-	- UnMock MOCK_WIDGET_DISPLAY_TEMPLATE_JSON into db with objects and with seeded data for test and or all lists
-		- One single object with all templates in JSON maybe? since there are not going to be multiple templates for same list object anyway
-			- Server can load it up and cache it like LT?
-		- Can it just make a default template if none is found?  (no they are all required)
 	- Once both lists are working:
+
+
+
+//READ THESE NOTES, IS IT ALL DONE NOW?
 		- abstract away the commonalities into other classes
 			- AyDataList containing
 				- AyaObjectFieldDefinitions