From f2563c87fa492859dc67eb4a21669a5112da26cb Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Tue, 26 Jan 2021 19:13:19 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 16 ++++++++++++---- 1 file changed, 12 insertions(+), 4 deletions(-) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index 5e7f4135..739f0756 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -96,14 +96,22 @@ todo: DataList view and filter are combined and this is wrong filter:[{column:"PartPartNumber",items:[{op: "=",value: "400735"}]}] } - # METAVIEW - This is intended to override the filter at client but it was in conjunction with existing filter which is problematic + # METAVIEW / VARIANT + NOTES: Metaview is used for two different thigns currently: + STATICALLY restricting a list to an always required filter like adm-users and cust-users and cust-customer-notes + solution is use variant system like picklist + DYNAMICALLY restricting a list to an on the fly filter like ShowAll + solution is solved by above changes and can provide alterantive filter programmatically any time + todo: remove metaview entirely at both ends - new system above has one filter and it's replaced by the old metaview so will this be ok or will it be an issue because something already written needs both? - probably not but check + todo: Modify DataList and implement Variant system just like picklists already does + must work with same capabilities shown in the current UnitPickList GetVariantCriteria which will work for the current STATICALLY filtered lists + (any list where the metaview was static and not optional but required for the view to work) + SEEDER + sample datalist is whack now