-
Notifications
You must be signed in to change notification settings - Fork 2.1k
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
Lazy prop not working #2846
Comments
Lazy was removed |
It's still in the API docs. Which now begs the question...how do we get content per component in a tabbed scene setup instead of mounting all of the components and making their requests all at once? Not sure how to accomplish this. |
@Donhv I'm sure it was working in an earlier 4.x release @JoePaulsenLyraHealth we add a |
+1 for this issue It's causing a major lag booting up the app since each tab screen handles a substantial amount of API calls for our app. When loaded one by one it's fine but when we load 6 tabs and their child components at once, it's a lot. |
I think this issue is a dup of #2296 |
|
Closed due inactivity |
Hi, thanks for the great router. I love the API. Unfortunately the lazy prop for Tabs has stopped working, I have used the prop as described in the API.
Version
Tell us which versions you are using:
Expected behaviour
I have a tab bar containing WebViews, I expect each WebView to be mounted only when it's navigated to.
Actual behaviour
Each WebView is mounted immediately, causing 4 WebViews to load at once, which slows down the app a fair bit.
Steps to reproduce
For non-obvious bugs, please fork this component, modify Example project to reproduce your issue and include link here.
<Tabs lazy>...</Tabs>
Here is what my router looks like:
The text was updated successfully, but these errors were encountered: