Thread
#compose
    t

    tad

    1 year ago
    Just to clarify: If I log something during recomposition of the top-level function of my Compose app, and that log occurs every 16 milliseconds, then one of the arguments to the top-level function has "changed" according to Compose?
    Zach Klippenstein (he/him) [MOD]

    Zach Klippenstein (he/him) [MOD]

    1 year ago
    Or some state read in that recompose scope might have changed
    t

    tad

    1 year ago
    Okay, so anything in a
    State
    container within the body of the function
    or read in the body of the function
    Zach Klippenstein (he/him) [MOD]

    Zach Klippenstein (he/him) [MOD]

    1 year ago
    it’s a little more complicated, but basically yea
    t

    tad

    1 year ago
    I know this has been asked before, but is there a way to figure out what state has changed?
    Zach Klippenstein (he/him) [MOD]

    Zach Klippenstein (he/him) [MOD]

    1 year ago
    you could put a breakpoint in the compose runtime’s snapshot observer i guess
    i can’t remember off the top of my head if there’s a convenient single place to do that, or where it is
    t

    tad

    1 year ago
    observeReads
    maybe
    c

    CLOVIS

    1 year ago
    React has a browser extension with a profiler that says exactly which component re-rendered and why. It'd be nice a Compose to have that as well.