Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
beat.editor
beat.editor
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 11
    • Issues 11
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 0
    • Merge Requests 0
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • beat
  • beat.editorbeat.editor
  • Issues
  • #124

Closed
Open
Opened Jun 11, 2018 by Jaden DIEFENBAUGH@jdiefenbaugh
  • Report abuse
  • New issue
Report abuse New issue

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!

Assignee
Assign to
State Management Refactoring
Milestone
State Management Refactoring
Assign milestone
Time tracking
None
Due date
None
2
Labels
hard maintenance
Assign labels
  • View project labels
Reference: beat/beat.editor#124