Establish what needs to be stored for each view #387
Labels
No labels
_CRITICAL_
API
app
backEnd
Blocked, waiting for further changes
bug
cleanup
close
design
duplicate
enhancement
feature request
frontEnd
help wanted
invalid
low priority
needs input
needs review
project documentation
question
research
reviewed
script
security
SQL
style
testing
topLevel
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Blocks
#391 Establish JSON structure for saving layouts
Andras/BoundlessFlowCampus2K
Reference
Andras/BoundlessFlowCampus2K#387
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Our goal is to be able to store each users layouts, including the size and location of views, as well as their contents. The contents will be different depending on view. We need to establish what to store for each view.
In my issue #289, I made it so every cards layout is saved along with their view. I commented in the code for the file Dashboard.js where this could be used for saving layout for users. Just an idea :)