You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When setting a key in useBucket to undefined (or null), the value doesn't get changed. It resolves to the previous value instead.
Removing the key works.
Google search terms
extend-chrome setting undefined
Describe the bug
When setting a key in useBucket to undefined (or null), the value doesn't get changed. It resolves to the previous value instead.
Removing the key works.
How do we reproduce?
This is my bucket
When I set the value to undefined (in async context), the value does not change in the valueStream
Expected behavior
The third run should print undefined instead of 1.
Actual behavior
The third run prints the last value: 1
Screenshots
Please complete the following information:
Additional context
Run in the background script
The text was updated successfully, but these errors were encountered: