Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Realm slows down app performance when updating multiple screen with react-navigation/native #6956

Open
shanoysinc opened this issue Jan 10, 2025 · 0 comments

Comments

@shanoysinc
Copy link

shanoysinc commented Jan 10, 2025

Problem

here is a discussion about the problem - #6490
Is there a solution to prevent useQuery from re-rendering a screen that you're not currently on? If so, could you please provide an example?

Solution

Whenever you trigger an update in Realm, useQuery gets updated, causing every screen in the bottom tab that uses useQuery to re-render. Is there a way to prevent this, so it only triggers a re-render when you visit that screen, and only if there was an update?

Alternatives

No response

How important is this improvement for you?

Would be a major improvement

Feature would mainly be used with

Local Database only

@shanoysinc shanoysinc changed the title Realm slows down app performance when update multiple screen with react-navigation/native Realm slows down app performance when updating multiple screen with react-navigation/native Jan 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant