Brendon Muir

All good @gagalago. Yes @julianrubisch, perhaps something like a proc or lambda that exposes the current scope as `self` so that it can be further refined?

Hi @fcheung, my instinct says that this is happening because the callbacks are relying on stale position information. After each item is moved you'd need to reload the rest so...

It might be that you'll need to not use `accepts_nested_attributes` and just manually loop the incoming list and update each list item one at a time (Which is what happens...

Ah I see, that's pretty tricky! Essentially your incoming positions become incorrect after the first one is saved (potentially). I don't see an elegant way around this. I don't think...

Hi @dlynam, I don't believe so. The point of the rank is that everything in the scope has a rank. You could try scoping in such a way that the...

It could be a coincidence but updating to Node 18 fixed this for me.

> It could be a coincidence but updating to Node 18 fixed this for me. Turns out I was too hasty. It still occurs in 18. Haven't checked 20.

I think in Rails 4, the assets are always precompiled with the cache busting string incorporated into the file name. So you can no longer reference assets without using the...

Hi @JanStevens, thanks for the bug report. Would you mind posting sql logs of what happens in both scenarios? Just to try and see the difference.

Looks like a bit of a mystery to me! :) For some reason the placeholder is being triggered as having been changed. I can't see anywhere in our code where...