Brandon Him
Can I see how you are invoking the Masonry component, along with your dataset?
@RyanKeepRunning `.map` doesn't mutate the exisitng array, you'll need to set it into it's own variable, or reassign. Still don't think this would necessarily fix your issue since you still...
@RyanKeepRunning Yeah I figured that wouldn't fix the warning, but at least we have the masonry rendering for you. For the warning, it seems the injector is getting complaints with...
Hey @RyanKeepRunning , Try pulling in the latest and see if this keeps the warnings at bay.
Sorry been trying to set up my Android environment but running through several issues that keep burning through my patience. Honestly, I don't get to allocate too much time on...
So I looked into this issue a while back, it really stems from an async call to load the image, but doesn't complete before the masonry view changes. This causes...
@ahmedjamshed what are "other two issues" exactly?
1. Left bias is default behavior, it will load based on what is resolved first. But with v0.5.0, not documented yet, you can use priority='balance', and it will do best...
2. Not entirely sure, I haven't done any testing on android. I would believe it has to do with some intermediate state changes during image fetching.
@ahmedjamshed The problem is bricks are resolved async so you'll probably run into issues there. Considering using redux to manage the async state, or migrate data.task to the new version...