From 0f60e20e13ffc1f5ed8f59977ef2f3c9fffdc02d Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Tue, 26 Feb 2019 21:05:16 +0000 Subject: [PATCH] --- ayanova/devdocs/todo.txt | 29 +++++------------------------ 1 file changed, 5 insertions(+), 24 deletions(-) diff --git a/ayanova/devdocs/todo.txt b/ayanova/devdocs/todo.txt index b652d583..0bdc75a4 100644 --- a/ayanova/devdocs/todo.txt +++ b/ayanova/devdocs/todo.txt @@ -14,31 +14,12 @@ TODO CLIENT STUFF TODO NEXT -Test separator allowing other weird characters in the template not as a function - -OK, I can make it display and take entry the way I want, but - - separator allows anything, not just what I specify (try it without a function directly in the template) - - Value comes back as text, I need to parse it whatever the case - -Maybe I can just allow free form entry and handle parsing, display in my own code?? -What about native components instead?? - -Find out how to do a currency and other types of numeric input -Make the currency and numeric fields work, then do the next stuff below: - -Currency field can be a v-text field with -Prefix set to the currency symbol and v-validate to ensure it's entered correctly -You can use the object form: -v-validate="{ required: true, decimal: [2, ','] }" - -https://github.com/baianat/vee-validate/commit/d9a3e97846aa47074e11bda4499ad539807ef0aa#commitcomment-25381793 - -Do I get back the proper currency value they entered that I can use even if it's comma separator?? -(Looks like I will need to parse it) - - - +DON"T code the user options with the currency symbol etc until after it's all been worked out client side. Use static values instad in locale. +Locale should fetch those settings the first time it sees they are not present so that they are refreshed upon use and are not stored in localstorage +(or should they be? anyway, can work that out later) +Other fields that are locale dependent +DateTime field next