Hi folks! Can you help me to find a thing from google’s docs for compose? I am pretty sure I saw tha...

# compose

[Vladimir Tagakov]

Hi folks! Can you help me to find a thing from google’s docs for compose? I am pretty sure I saw that google recommends to pass multiple callbacks to a composable function instead of using a single one with an action passed as a parameter. In other words they suggest to write:

@Composable 
fun MyComposable(somethingHappened: () -> Unit, otherHappened: () -> Unit)

instead of

@Composable
fun MyComposable(onAction: (ActionSealedClass) -> Unit)

Can’t find a proof for that in the docs or guidelines tho 😞 Can anyone help?

[Zach Klippenstein (he/him) [MOD]]

I don’t think i’ve ever seen/heard this recommendation

[agrosner]

im guessing its in the context of state and instead of passing MutableState as parameters, pairing it with callback and value as separate params:

@Composable
fun MyComposable(value: ActionSealedClass,onUpdate: (ActionSealedClass) -> Unit)

https://developer.android.com/jetpack/compose/state#state-hoisting

[Vladimir Tagakov]

Nope, that’s not the case 😞
Alright, I can’t find anything related, so I think it is either phantom memory or a change in the docs. Thank you, folks!

[yschimke]

I think API guidelines are https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:compose/docs/compose-api-guidelines.md?q=compose%20api%20guidelines and https://cs.android.com/androidx/platform/frameworks/support/+/androidx-main:compose/[…]pose-component-api-guidelines.md?q=compose%20api%20guidelines

[yschimke]

Nothing clear there.

[Vladimir Tagakov]

Yep, they don’t mention anything like that

[Vladimir Tagakov]

And also for some reason I can’t see the history of those files

[Arkadii Ivanov]

There is "History" button at the bottom of the page. Does it help?

[Vladimir Tagakov]

=\ I was lookig here: https://android.googlesource.com/platform/frameworks/support/+/androidx-main/compose/docs/compose-api-guidelines.md

And didn’t notice that Yuri’s link is to <http://cs.android.com|cs.android.com> instead. I’ll take a look, thank you, but I doubt I’ll be able to find it still :)

[Vladimir Tagakov]

It didn’t help 😞

[dewildte]

I swear I have seen the same advice somewhere too.
Not sure if it showed up in a code workshop or what.
But it did say to favor multiple lambdas over sealed classes and enums.
I think the reasoning has to do with it being easier to refactor and implement thanks to it's simplicity.