multiple trackings on same component does not work about overmind HOT 5 CLOSED

You need to clearTrackState in the reverse order you started tracking it. So in your doRender() try this:

function doRender() {
  let trackId = trackState()
  app.state.Sort.Field1
  let trackId2 = trackState()
  app.state.Sort.Field2
  let paths2 = clearTrackState(trackId2)
  let paths = clearTrackState(trackId) 
}

from overmind.

thanks...but its a bit more complex because the second render may happen or not and i don't have direct control over it.
Shouldn't it work as well with 2 subsequent (= not nested) trackings as well? i would expect that because i can update the listeners with paths as many times as i want.

from overmind.

thats the failing testcase i've created. maybe it helps:

test('listener should be called after updating paths', () => {
  const tree = new ProxyStateTree({
    foo: 'bar',
    bar: 'baz',
  })
  const state = tree.get()
  let updateCount = 0
  // access foo and track it
  let trackId = tree.startPathsTracking()
  state.foo
  let paths = tree.clearPathsTracking(trackId)
  const listener = tree.addFlushListener(paths, () => {
    updateCount++
  })
  // access bar and track it
  trackId = tree.startPathsTracking()
  state.bar
  paths = tree.clearPathsTracking(trackId)
  listener.update(paths)
  // mutating foo should call listener
  tree.startMutationTracking()
  state.foo = 'bar2'
  tree.clearMutationTracking()
  tree.flush()
  expect(updateCount).toBe(1)
})

from overmind.

I don't think the test case should pass.
You are explicitly calling clearPathsTracking after accessing state.foo and therefore these paths are cleared and should not leak into the next clearPathsTracking.

startPathsTracking/clearPathsTracking should be called before and after each render cycle is done. This allows to differentiate the various nested render calls and don't leak path tracking to a parent.

Additionally the behaviour of listener.update ensures that only the tracked paths are observed for changes and there are no stall paths that will be tracked indefinitely.

from overmind.

hmm yes, i did something wrong as it looks like.
after reverting everything back to regular "nested" - tracking it works as expected :)
i think i went down the wrong route after i've recognised that a property wasn't tracked but it was accessed. now its still not tracked and i need to elaborate on that.
thanks for pushing me into the right direction :)

from overmind.