oh heck yeah <https://github.com/theapache64/rebugger>

# compose

[Colton Idle]

oh heck yeah

https://github.com/theapache64/rebugger

[andylamax]

Good job

[Jaime]

nice

[andylamax]

Although looks like at the moment, this is best posted in #compose-android

[Colton Idle]

keep forgetting they made that split.

[ephemient]

it's only Android specific because of its build setup and the use of android.util.Log, and its hack for getting composableName is JVM-specific; that aside, the core idea would be implementable in compose-multiplatform

[Shakil Karim]

i hope if they can add something like "Self._printChanges()" from SwiftUI in Compose.

[shikasd]

Note that the function can also be recomposed because of the inner state change, which is a bit harder to track :)

[ephemient]

@Shakil Karim https://stackoverflow.com/a/69859435 that's not meant to be used by SwiftUI code

[Colton Idle]

@theapache64 looks like you've got a multiplatform freature request buddy. 😅

[theapache64]

@Colton Idle 😄 uh ho!! i didn’t expect a multiplatform request this soon. Tracking it here : https://github.com/theapache64/rebugger/issues/2 (please vote)

[theapache64]

@shikasd I am thinking of creating an IDE plugin to do that https://github.com/theapache64/rebugger/issues/1. That’d fix it right? or you’re talking about a different problem ?

[shikasd]

Depends on what you want to track, rebugger is tracking call site changes, I was thinking more along the lines "what read states are causing current scope to recompose"

[shikasd]

It is fairly frequent to pass the same lambda/state as a parameter, so you won't see a difference on the callsite, only if you track state reads

[theapache64]

aaah..got it. that’s something i wanna look little more