This commit is contained in:
@@ -6,19 +6,14 @@ eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpYXQiOiIxNTcxODU5OTU0IiwiZXhwIjoiMTU3MjQ
|
||||
## IMMEDIATE ITEMS
|
||||
|
||||
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:
|
||||
- Add controller for it with validation callable from DataListTemplate (Validate(string template) method)
|
||||
- Add validation in DataListFetcher to ensure template is still valid (commented with TODO)
|
||||
|
||||
Rename DataFilter model / table etc to DataListFilter
|
||||
Make up the USER datalists
|
||||
|
||||
Make up the user Object datalists
|
||||
DataList object naming scheme, should it be prepended so they all align well and are easy to spot in the project or since they are exposed should it not?
|
||||
- Cadillac problem?
|
||||
|
||||
DataList object naming scheme, should it be prepended to they all align well?
|
||||
|
||||
AyaFormFieldDefinitions still has UI field datatype in it, but I don't think I'll need it so ponder this by looking at tests and client and make a decision
|
||||
- Consider if there is some possible future use for this or YAGNI
|
||||
|
||||
|
||||
INTEGRATION TEST UPDATE Update tests when appropriate (when it's working fully and not mocked)
|
||||
|
||||
Reference in New Issue
Block a user