Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • beat.editor beat.editor
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 11
    • Issues 11
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • beat
  • beat.editorbeat.editor
  • Issues
  • #124

Closed
Open
Created Jun 11, 2018 by Jaden DIEFENBAUGH@jdiefenbaughContributor

State management refactoring

Thought we already had an issue open for this but I guess not.

Right now the object editors are using a cache state field to hold the unsaved changed. These changes aren't propogated to the redux store until the user clicks 'save', which will also save to the prefix. There's no reason to have a state cache and the redux store anymore.

Instead of using the editors' states' cache fields to store unsaved changes, just use the redux store!

To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking