Does it make sense to use Batch Requests and Dedupe Requests plugin in the same RPCLink?

[Axedyson]

I'm trying to understand both of these plugins especially the dedupe requests plugin. What kind of example of requests would be deduped given that the only group defined is for method: 'GET'? Is it simply all 'GET' requests that are submitted at the exact same time? I'm planning to use tanstack query so I guess using this RPC deduping plugin is unnecessary as tanstack query does it automatically I think.

Also can the dedupe request and batching requests plugin work together on the exact same group? Does it even make sense to use them like that, I assume they will conflict.

[unnoq]

• Dedupe + Batch work well together. Just configure each one correctly, and they work.
• Dedupe plugins can be redundant in TanStack Query because it has its own deduplication mechanism.

[Axedyson]

@unnoq can you provide me an example of code that uses tanstack query where the batch plugin will be in use? I'm using solid tanstack query with orpc.

I found this: https://tanstack.com/query/latest/docs/framework/solid/guides/parallel-queries
but I'm not sure the batch plugin will be activated in that scenario. If there is no scenario where tanstack query will be able to trigger the batch plugin, then there is no need to use the batch plugin for me at least

[unnoq]

@Axedyson

• oRPC dedupe plugin will consider dedupe requests in the same call stack
• dedupe take no effect when combine with tansatck-query because tanstack-query has its own dedupe, everything still work. Everything you need is setup an oRPC project and try it yourself. if face any problem please open an issue on github.

[Axedyson]

I was actually referring to the batch plugin, not the dedupe plugin in my previous reply, I'm just curious how tanstack query would trigger the effect of the batch plugin in action. But I will test the batch plugin myself and see how it works with tanstack query.

[unnoq]

@Axedyson like dedupe plugin, batch plugin also batch requests in the same call stack

[Axedyson]

Aah I get it now! This is smart:

export function defer(callback: () => void): void {
  if (typeof setTimeout === 'function') {
    setTimeout(callback, 0)
  }
  else {
    Promise.resolve()
      .then(() => Promise.resolve()
        .then(() => Promise.resolve()
          .then(callback)))
  }
}

Though I don't know how this works:

    Promise.resolve()
      .then(() => Promise.resolve()
        .then(() => Promise.resolve()
          .then(callback)))