refactor(sidebar state): moved onto TinaCMS #649
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Looking for everyone's thoughts on this.
I started mulling over the Sidebar state after checking out @weibenfalk's thoughts on configuring the text on the Save/Reset buttons.
This change reifies the sidebar state and places it on the TinaCMS class as a property. I think this approach has a couple benefits:
SidebarContext
in the React app, instead relying on the pre-existinig CMSContext.Here is how it would be used.
Checking sidebar state:
Changing sidebar state:
Subscribing Option 1
Subscribing Option 2: