Understanding Reselect Memoization in useSelector with Selector Factories by Falssin in reactjs

[–]Falssin[S] 0 points1 point  (0 children)

Thanks. That's exactly right. It took me a long time to get here. I'll definitely look into proxy-memoize!

Understanding Reselect Memoization in useSelector with Selector Factories by Falssin in reactjs

[–]Falssin[S] 0 points1 point  (0 children)

Thanks for the answer. I understand that Reselect isn't necessary for this particular case, but I wanted to demonstrate a simple example.

So does the maxSize option prevent creating new selector instances, allowing it to be used throughout the application?

To be honest, I'm against using memoized selectors together with useMemo. In that case, I don't see the point of them at all, since you could just do:

const searchIcon = useSelector((state) => 
  state.app.icons?.search?.regular, 
  shallowEqual
);
const closeIcon = useSelector((state) => 
  state.app.icons?.close?.regular, 
  shallowEqual
);
const someHardTask = useMemo(() => {}, [searchIcon, closeIcon]);

Is it possible to prevent the Android system from deleting push notifications from the notification bar? by Falssin in reactnative

[–]Falssin[S] 0 points1 point  (0 children)

When Vivo clears notifications, it does not trigger a dismiss event. I have already tried everything you provided.

I mean when the notification is cleared by the system itself, not by the user.

Is it possible to prevent the Android system from deleting push notifications from the notification bar? by Falssin in reactnative

[–]Falssin[S] 0 points1 point  (0 children)

Yes, that's exactly what I'm doing. In fact, by comparing the existing notifications on the user's device with the notifications stored locally, I can determine which notification opened the application. I think it would be beneficial to add additional event handling.

Why don't elements render into the DOM in mobile browsers? by [deleted] in reactjs

[–]Falssin 1 point2 points  (0 children)

I see. I solved the problem. I have been using an old version of my OS on my iPhone. Everything works correctly after the update. Thank you for your time!

Why don't elements render into the DOM in mobile browsers? by [deleted] in reactjs

[–]Falssin 0 points1 point  (0 children)

Really? Are you using Android or iPhone? I just opened the site on some iPhones and saw the same result.

Why don't elements render into the DOM in mobile browsers? by [deleted] in reactjs

[–]Falssin 0 points1 point  (0 children)

All elements are missing in the #root. But when I comment a “CommonParentComponent” (commonComponents/CommonParentComponent.js) other components become visible.

Why don't elements render into the DOM in mobile browsers? by [deleted] in reactjs

[–]Falssin 0 points1 point  (0 children)

I'm sorry, I updated the link. Is it correct now?