From 32c629bfd90a82cb0730158fd1b05af1750b562b Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Fri, 21 May 2021 23:33:13 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 36 +----- ayanova/src/components/tax-picker.vue | 103 ------------------ .../components/work-order-item-expenses.vue | 43 +++++++- 3 files changed, 40 insertions(+), 142 deletions(-) delete mode 100644 ayanova/src/components/tax-picker.vue diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index 61b38595..46c7dbcb 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -341,44 +341,12 @@ todo: many biz objects are not using new PUT methodology CURRENTLY DOING: -todo: do expenses, part and travel objects: model, schema, FormFieldReference, biz object, front end UI todo: remove taxcode edit control once done -Move back to original linked tax codes with hybrid history preservation system - BACKEND: - - - FORM FIELD DEFINITIONS - Edit to remove fields and add manual override field back - - Workorder - TAXES - remove all the code that preserves the tax info like name and values and move back to the single ID - update the calcs code to fetch the tax code to apply it - put back the tax code viz field - update the FormFieldReference to remove the tax code shit - - RATES - Rates are fixed now so no need to store redundantly except user can override so...? - How about a single override field that is null by default and if an entry is made that takes over from the default rate - To clear it they simply empty the field and if null the viz calcs will use the rate price instead - - CALCS / VIZ - Calcs are now all Viz fields populated on the fly and not stored in the wo - Override field is used if non-null otherwise the rate is pulled and used for the calc - - - - FRONT: - Revert back to viz fields and remove snapshotted fields - switch back to simple picklist for taxes - Expose the override field - - - HYBRID - mostly fixed with a few things snapshotted that are likely to change regularly - Impermanent things: - prices of things - addresses +todo: part prices are going to change / volatile, are they snapshotted? (cost/charge) + rates and taxes are ok to not snapshot, their values are protected once used but parts are volatile and should be snapshotted diff --git a/ayanova/src/components/tax-picker.vue b/ayanova/src/components/tax-picker.vue deleted file mode 100644 index 8591e45d..00000000 --- a/ayanova/src/components/tax-picker.vue +++ /dev/null @@ -1,103 +0,0 @@ - - diff --git a/ayanova/src/components/work-order-item-expenses.vue b/ayanova/src/components/work-order-item-expenses.vue index 3fa3eba3..4c8c590b 100644 --- a/ayanova/src/components/work-order-item-expenses.vue +++ b/ayanova/src/components/work-order-item-expenses.vue @@ -278,7 +278,7 @@ > - + --> + + +