This commit is contained in:
@@ -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
|
||||
|
||||
Reference in New Issue
Block a user