Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Default value ignores/overwrites previous localStorage state
See original GitHub issueHey there,
I am confused by the behavior of the defaultValue prop. I would imagine that say for the key of ‘color’, setting a defaultValue of ‘red’, would only set the attribute to ‘red’ if no other value was set for color already (in localStorage in my case).
Here’s an example of what I find confusing:
https://codesandbox.io/s/purple-morning-1z2or?file=/src/App.js
This is confusing behavior IMO. I don’t think the pre-existing localStorage keys should be clobbered by something that is named a defaultValue.
Thoughts @astoilkov ?
Issue Analytics
- State:
- Created 2 years ago
- Comments:13 (7 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Awesome thanks @astoilkov !!
Wow. That’s actually a very bad bug. I fixed it and published a new release.
Thanks, @tnrich!
Closing this issue.