admin/raven-client
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Browse Source
This commit is contained in:
John Cardinal
2021-09-22 17:07:42 +00:00
parent 2febee790f
commit 76cb0ac8be
2 changed files with 10 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

3
ayanova/src/api/ayatype.js
View File

@@ -1,8 +1,7 @@
export default { export default {
NoType: 0, NoType: 0,
Global: 1, Global: 1,
//corebizobject FormSetting: 2,
UNUSED_2: 2,
//corebizobject //corebizobject
User: 3, User: 3,
ServerState: 4, ServerState: 4,

9
ayanova/src/views/home-schedule.vue
View File

@@ -370,6 +370,15 @@
TODO NEXT: 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 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 Settings should be for the FORM, not the user so that a user can have different settings in personal schedule vs svc-schedule etc