Well, I burnt most of today figuring this out and working around the edges of it.

The moral seems to be: don't push the "get rid of data" change to stripes-connect master until after the things that use data have all been updated.

Yep, looking good.

Sheesh, what a waste of time this is turning out to have been.

Here's what happened. When I was trying to debug this problem (using the most recent stripes-connect), I looked at component state in the browser tools, and found that props.data and props.resources were both empty – so I assumed that switching from data to resources () wouldn't help.

In fact, though, I was only seeing the state during the initial render. In subsequent calls to the same render method, after the Okapi response has come in, resources is set – and data is not, due to its deliberate removal. (I could quibble and say that it should not have been removed until and all the similar tasks are complete, but let it pass.)

Anyway – it now looks like will solve this problem after all. I was going to take that issue and make the relevant changes, but it looks like Michal was ahead of me. I'll check how his changes work out for me, and then it may be that this can be closed.

I think this may have been an error on my part – hurrah if so!

More details if I turn out to be correct about that.

Assigned to since it's his commit and he might know what the problem is.

Moved directly into sprint24, since this is a pretty fundamental breakage.