fix: reactive storage infinite loop #181
Merged
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
tmkx
changed the title
adao
reviewed
Jun 25, 2024
| @@ -132,7 +132,14 @@ export function useWebExtensionStorage<T>( | |||
| data, | |||
| async () => { | |||
| try { | |||
| await (data.value == null ? storageInterface.removeItem(key) : storageInterface.setItem(key, await serializer.write(data.value))) | |||
| if (data.value == null) { | |||
| storageInterface.removeItem(key) | |||
There was a problem hiding this comment.
Noticed that promises no longer get awaited. Not sure how big of a deal that is.
This was referenced Jun 27, 2024
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
Multiple triggering of reactive data updates by the same function interspersed with asynchronous functions.
Causing multiple triggers of the watch function in a short period of time
Linked Issues