-
-
Notifications
You must be signed in to change notification settings - Fork 2.2k
feat: getLazy prop for bottom-navigation #3433
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
Conversation
|
The mobile version of example app from this branch is ready! You can see it here |
1 similar comment
|
The mobile version of example app from this branch is ready! You can see it here |
|
That PR will need the following changes in the material-bottom-tabs repository once the stable version is released. |
|
The mobile version of example app from this branch is ready! You can see it here |
|
The mobile version of example app from this branch is ready! You can see it here |
|
The mobile version of example app from this branch is ready! You can see it here |
Co-authored-by: Luke Walczak <lukasz.walczak.pwr@gmail.com>
Co-authored-by: Luke Walczak <lukasz.walczak.pwr@gmail.com>
Co-authored-by: Luke Walczak <lukasz.walczak.pwr@gmail.com>
Co-authored-by: Luke Walczak <lukasz.walczak.pwr@gmail.com>
Summary
Fixes #3085
Introduces
getLazycallback prop which allows the user to set lazy for each screen as they want leveraging therouteparameter received in the callback. If user wants to set lazy for every screen, they can simply returntruefrom the callback.Usage:
Test plan
Unit test coverage 🧪