This commit is contained in:
@@ -60,4 +60,14 @@ Back AND front end
|
||||
- REPORTS (FUTURE) Should send the customized templated display name field to the reports as well as all the regular including name fields
|
||||
- This is because users will likely want that for many reports
|
||||
- Kind of a calculated field
|
||||
- Default templates come with Raven, user can customize further
|
||||
- Default templates come with Raven, user can customize further
|
||||
|
||||
MOCK TEMPLATE
|
||||
{
|
||||
columns:[
|
||||
|
||||
],
|
||||
mini:[
|
||||
|
||||
]
|
||||
}
|
||||
@@ -20,6 +20,15 @@ REALLY MAKING MORE PROGRESS WHEN CLIENT DEV DRIVES BACKEND DEV, STICK TO THAT!!
|
||||
-----------------------
|
||||
|
||||
GRID LISTS TODO NOW:
|
||||
|
||||
- FormAvailableFields rename to ObjectFields
|
||||
- It was previously used for only custom forms, but it also needs to exist for creating list templates
|
||||
- Some list templates don't have exact corresponding biz object as they are compound or made up so need for all lists as well
|
||||
- Need filterable property added so can control what can be filtered
|
||||
- Need sortable property so can control what can be sorted
|
||||
- This will now drive both form customization and list filters and possibly other shit in future
|
||||
- Remove FilterOptions in list objects and use this instead
|
||||
|
||||
- Return JSON and internally work with JSON so the list can return dynamic object
|
||||
- https://devblogs.microsoft.com/dotnet/try-the-new-system-text-json-apis/
|
||||
- https://docs.microsoft.com/en-us/dotnet/core/whats-new/dotnet-core-3-0#fast-built-in-json-support
|
||||
|
||||
Reference in New Issue
Block a user