WIP: Allow for persistence in Cytoscape component. #121
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@ManInFez I haven't forgotten about this PR! There's a few things I wanted to get done (update react/react-dom to 16, update docgen, and actually add persistence) before reviewing this. I'll ping you again when I'm ready to review this. |
|
I'll review this once #125 is merged |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
About
This PR is about solving the issue of persisting component information natively.
resolves #113
Description of changes
Pre-Merge checklist
npm run build:all.Reference Issues
closes #113
Other comments
Currently very much a WIP