android/ui: use compose getValue syntactic sugar consistently #367
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
agottardo
approved these changes
May 3, 2024
kari-ts
approved these changes
May 10, 2024
Updates #cleanup "by stateFlow" is syntactic sugar for" = stateFlow.value" and is more idiomatic. There should be no functional difference here. Just\ changed where it can be for consistency. Signed-off-by: Jonathan Nobels <[email protected]>
barnstar
force-pushed
the
jonathan/cleanup-2
branch
from
214cd41
to
6a64d67
Compare
kari-ts
pushed a commit
that referenced
this pull request
May 29, 2024
Updates #cleanup "by stateFlow" is syntactic sugar for" = stateFlow.value" and is more idiomatic. There should be no functional difference here. Just\ changed where it can be for consistency. Signed-off-by: Jonathan Nobels <[email protected]>
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.
Updates #cleanup
"by stateFlow" is syntactic sugar for" = stateFlow.value" and is more idiomatic. There should be no functional difference here.