Looking into this, the SDK is not currently utilizing the [conversation eager loading capabilities of the API. It's actually making additional http requests to fetch the threads, assignee, etc. for each conversation. So if 50 conversations are loaded, that's 50 additional requests for each eagerly loaded entity that's being made. On top of that, loading page 3 executes all of that all over again. This is far less than ideal for a lot of reasons. I'll put this on our backlog to visit in the future.
I'm curious if this was resolved, or if there are plans to? Thanks!
Hey @bkuhl,
I noticed over here, you mentioned this:
I'm curious if this was resolved, or if there are plans to? Thanks!