java.lang.ClassCastException when the parent resolver of a batch resolver returns a seq. about pathom3 HOT 2 CLOSED

Thanks for this report, I have made some changes around this behavior with batches.

Code for the changes is at 721d142

First I like to talk about the problem. The problem of seqs (or sets), is that they are data structures that don't support indexed update (can't assoc-in or update-in some specific element of the collection). This is a problem for batching, because batch runs kind of "outside" the entity, and then it has to be merged back in. This merge back in is the step in which I need the indexed update. Vectors can do this just fine, but seqs and sets can't.

The error on stack is related to the attempt of doing assoc-in on a seq (or set).

Now I change the behavior, and if you run this same again, you should see the correct response, and some warnings about batch disabled. Now, when I start processing something that's not batch compatible, I mark the env, and if you try to do batch in one location like this, it won't try to batch, it will use the batch resolver as a non batch one (send a list with one element, pick the first result). This way it will work as if you don't have batch, but works. And if this happens you get a warning message to let you know your batch is not happening.

I also updated the docs on batching to reflect this new knowledge, you can it at: https://pathom3.wsscode.com/docs/resolvers/#unsupported-batch

from pathom3.

Thanks a lot for this Wilker. Very happy with your solution 👍

from pathom3.