When using maverickjs adapter, using tick() inside flushSync() doesn't work as expected

[morgs32]

I was hoping that if I did an insert into a collection like this:

import { tick } from 'maverickjs/signal'

...
const resources = useReactivity(() => collection.findMany({}).fetch()})
const [state, setState] = useState(0)

console.log(resources)

onClick={() => {
   flushSync(() => {
      collection.insert(resource)
      tick()
   })
  setState(state+1)
})

That the next time it logged resources it would include the new one...

Here is a sandbox, without the flushSync which maybe is irrelevant to the question??
https://codesandbox.io/p/sandbox/empty-dawn-q3qd4t

[maxnowack]

Reactive updates in SignalDB are always scheduled to the next tick with setTimeout(() => …, 0) to improve performance. So I think what you want to achieve wouldn't work.
Maybe you could explain your use case a bit more. I'm pretty sure there is another solution 🙂

[maxnowack]

That's something I also think about at the moment 😀 I'll try to figure out what my initial intention was with this and see if I could get rid of it.

[maxnowack]

I added the delay in #575 as a performance improvement when there were many changes. The issue was that the indices were rebuilt after every single change. However, since the trade-offs are significant compared to this relatively edge case of massive sequential updates, I’m removing the delay in #908. This PR also includes a .batch() method to ensure performance during large-scale updates.

[morgs32]

👍 appreciate the investigation and thumbs up for your solution. I can totally see using the .batch() method too.

[maxnowack]

Fix released in v0.19.0 🎉