From c3ea911e1ed36f398819c35b8c5117aa29e8786c Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Wed, 27 Nov 2019 19:38:59 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 18 ++---------------- .../src/components/custom-fields-control.vue | 2 +- 2 files changed, 3 insertions(+), 17 deletions(-) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index 11ecd01c..1c68da75 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -46,22 +46,8 @@ CURRENT TODOs =-=-=-=-=-=-= - -TODO: In a few places in my own components I'm emitting multiple events for changes when possibly it should just be one - - Determine which events are being emitted in custom controls - - Research those events to see what they actually mean to VUE / VUETIFY - - Remove any extraneous or unnecessary events (even just to test if they are required) - -TODO: Change detection dirty tracking not quite right on the widget form: - - Make a new record then click into each field and edit it and notice the save button doesn't enable - - But, if you tab between controls it *does* enable so somehow it's not firing a change event or something - -TODO: Error handler is not recognizing the same error over and over again and it should stop after so many dev errors - -TODO: Make sure can easily make new record in Widget form before getting into deeper stuff or making any other object forms. - -TODO: UI would be greatly enhanced if server defined form customization rules for required fields both Custom and regular were incorporated into client end before roundtripping to the server - - Right now it has to save the record to get the return errors about required fields, that is shit. The client is easily able to tell what is required in the form customization so it should be able to surface that up front +TODO: UI would be greatly enhanced if server defined form customization rules for required fields REGULAR fields only (custom are already handled) were incorporated into client end before roundtripping to the server + - Right now it has to save the record to get the return errors about required regular fields, that is shit. The client is easily able to tell what is required in the form customization so it should be able to surface that up front - This will save bandwidth and annoyance factor 1000 for people TODO: Widget edit form, new record sb time and dates pre-filled in? Server involved? How to handle new record initial date set? diff --git a/ayanova/src/components/custom-fields-control.vue b/ayanova/src/components/custom-fields-control.vue index 9700b8b8..0619d431 100644 --- a/ayanova/src/components/custom-fields-control.vue +++ b/ayanova/src/components/custom-fields-control.vue @@ -241,7 +241,7 @@ export default { //emit the new data so it syncs with the parent source var ret = JSON.stringify(cData); - //THis is absolutely required no idea why though + //THis is absolutely required or it won't save any changes, no idea why though this.$emit("update:value", ret); //this.$emit("input", ret); //always in UTC //this triggers the onchange routine in the parent form