From bded73c6e2c21d3f785ca480956fd70ecc411a84 Mon Sep 17 00:00:00 2001 From: John Cardinal Date: Thu, 23 Sep 2021 00:23:45 +0000 Subject: [PATCH] --- ayanova/src/views/home-schedule.vue | 33 +---------------------------- 1 file changed, 1 insertion(+), 32 deletions(-) diff --git a/ayanova/src/views/home-schedule.vue b/ayanova/src/views/home-schedule.vue index 1dd0068f..f6d5e573 100644 --- a/ayanova/src/views/home-schedule.vue +++ b/ayanova/src/views/home-schedule.vue @@ -422,39 +422,8 @@ /* 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 - persist, imminentize - Save / load from server (or locally only? as formSettings.saved)?? - saved with device or saved with account is the heart of it - -Settings: - wo color choice - wo show - reminders show - reviews show - weekdays to show - start time - intervals - interval slices - - - - - - todo: ### find all trans keys and make sure they are fetched in initform ### + TESTING: Test here locally and check for layout issues while doing it on all devices drag/extend in all views working?