From 76cb0ac8be814be855bdab4ba483ddfc1fa95e12 Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Wed, 22 Sep 2021 17:07:42 +0000 Subject: [PATCH] --- ayanova/src/api/ayatype.js | 3 +-- ayanova/src/views/home-schedule.vue | 9 +++++++++ 2 files changed, 10 insertions(+), 2 deletions(-) diff --git a/ayanova/src/api/ayatype.js b/ayanova/src/api/ayatype.js index 810e7f98..44b0c912 100644 --- a/ayanova/src/api/ayatype.js +++ b/ayanova/src/api/ayatype.js @@ -1,8 +1,7 @@ export default { NoType: 0, Global: 1, - //corebizobject - UNUSED_2: 2, + FormSetting: 2, //corebizobject User: 3, ServerState: 4, diff --git a/ayanova/src/views/home-schedule.vue b/ayanova/src/views/home-schedule.vue index 9ebd63b5..f9e72ab6 100644 --- a/ayanova/src/views/home-schedule.vue +++ b/ayanova/src/views/home-schedule.vue @@ -370,6 +370,15 @@ TODO NEXT: +Determine all settings required to persist (try to think of shared schedule too becuase want to use the same basic structure so one path to api) + Store and retrieve as a single json object? + then could re-use for potentially other things + Like a route that stores per userid and formkey a single json object, null if none + on change of settings persists when settings form closes + does this supersede some user options? + + + Settings form Settings should be for the FORM, not the user so that a user can have different settings in personal schedule vs svc-schedule etc