Feature/add optional serialization to use storage #439
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.
The main feature is to support a custom serializer/deserializer without introducing breaking changes.
This should fix:
useLocalStorage
anduseSessionStorage
is not supporting JSSet
andMap
#308This PR in the last commits also fixes missing stuff:
The work was always done the same on both
useLocalStorage
anduseSessionStorage
(not DRY though 😅 it will be refactored)Feedback and review are welcome