Hi @selbekk
, thanks so much for your post and this comment reply. When I tried to implement this class-based version, I encountered the following (unfamiliar) error:
Error: Objects are not valid as a React child (found: object with keys {type, key, ref, props, _owner, _store}). If you meant to render a collection of children, use an array instead.
I'm trying to track down this error, but do you have any suggestions to point me in the right direction?
Thanks @selbekk
, for your reply. That was indeed the case - I was implementing the class-based version in the wrong place within the component hierarchy. The quick fix was simply to locally store only the single piece of state that needed to persist, rather than the entire state object. Works like a charm, and I'm grateful for this post.
Hi @selbekk , thanks so much for your post and this comment reply. When I tried to implement this class-based version, I encountered the following (unfamiliar) error:
Error: Objects are not valid as a React child (found: object with keys {type, key, ref, props, _owner, _store}). If you meant to render a collection of children, use an array instead.
I'm trying to track down this error, but do you have any suggestions to point me in the right direction?
That happens when you try to render a regular object as children. I’d have to see more of the related code to be of any assistance
Thanks @selbekk , for your reply. That was indeed the case - I was implementing the class-based version in the wrong place within the component hierarchy. The quick fix was simply to locally store only the single piece of state that needed to persist, rather than the entire state object. Works like a charm, and I'm grateful for this post.
Probably need to JSON.stringify that object to store the data in local storage.