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
Describe the bug
I have a collection of items which I pass into Masonry. When I delete an item, recreate the collection, and thus rerender the component holding the Masonry, I get "WeakMap key undefined must be an object".
To Reproduce
Go to the appropriate route/component (loader loads the items, Masonry loads successfully)
Click on the delete button of the item (asynchronously, item is POST-ed to the relevant route, which reruns the loader, returning a new collection)
The error appears
Expected behavior
The component should render successfully.
Screenshots
1.
Desktop (please complete the following information):
OS: Windows
Browser Firefox / Chrome
Version Firefox 130.0 / 128.0.6613.138
Smartphone (please complete the following information):
(not tested)
Additional context
(May or may not be relevant.) The collection is retrieved by a React Router Ioader into the component via the useLoaderData hook; i.e. not some internal state.
I delete the item using an async function; POST-ing to the React Route of the component and thus triggering the loader to run again, and the component to re-render.
Describe the bug
I have a collection of items which I pass into
Masonry
. When I delete an item, recreate the collection, and thus rerender the component holding theMasonry
, I get "WeakMap key undefined must be an object".To Reproduce
Expected behavior
The component should render successfully.
Screenshots
1.
Desktop (please complete the following information):
Smartphone (please complete the following information):
(not tested)
Additional context
(May or may not be relevant.) The collection is retrieved by a React Router Ioader into the component via the
useLoaderData
hook; i.e. not some internal state.I delete the item using an async function; POST-ing to the React Route of the component and thus triggering the loader to run again, and the component to re-render.
Stack trace:
The text was updated successfully, but these errors were encountered: