Hoist state changing of screen
#1675
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
veyndan
commented
Nov 9, 2023
| @@ -44,12 +45,11 @@ class TestContext( | |||
|
|
|||
| @Composable | |||
| fun TestApp(context: TestContext) { | |||
| val screenKeyState = rememberSaveable { mutableStateOf<String?>(null) } | |||
| val screenKey = screenKeyState.value | |||
| var screenKey by rememberSaveable { mutableStateOf<String?>(null) } | |||
There was a problem hiding this comment.
Using property delegation to reduce the risk of this happening again.
Per [the documentation](https://developer.android.com/jetpack/compose/state#state-hoisting), It's bad practice to pass `MutableState`'s down as parameters. Per their guidance, the parameter has been split between two: `screen` and `onScreenChange`.
veyndan
force-pushed
the
veyndan/2023-11-09/hoist-screen-change
branch
from
5efbe41 to
c40afc7
Compare
JakeWharton
approved these changes
Nov 9, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Per the documentation, It's bad practice to pass
MutableState's down as parameters. Per their guidance, the parameter has been split between two:screenandonScreenChange.