Replace local storage with zustand for new template flow #420
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
| } | ||
| }; | ||
|
|
||
| const handleUnmount = () => { | ||
| setDrawnFields(new Set()); | ||
| setSelectedField(null); | ||
| } | ||
| // TODO: Ask Kevin what this is for, it's not clear |
There was a problem hiding this comment.
oh after we annotate i noticed that we need to clear those fields to prepare the the next annotation
knguyenrise8
approved these changes
Nov 22, 2024
|
pulled local and saving templates do not work but im guessing thats in progress. |
Clarifying - this means it does not persist to database? That is correct, this is a precursor to storing all the template data in the db so it is still writing that to local storage. Seemed prudent to split them up. |
4 tasks
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.
Description
Replaces local storage for intermediate storage during the new template flow.
Does not replace storing of the final templates or the storage for extract flow (those are follow ups)
Screenshots (if applicable)
N/A
Related Issues
#391
Checklist