oRPC WebSocket connection params

[bnussman]

Hello!

Congrats on oRPC, it looks like an awesome tool that I may have to start using! 👏🏼

In my projects, I pretty heavily rely on lazy mode (on the client) and connectionParams to authenticate my Websocket connections when the connection starts.

I'm considering adopting oRPC but my questions are

• Does oRPC have a concept of lazy mode?
• Does oRPC have a concept of connectionParams?

Wanted to check here because I didn't see much in the docs about this

Here are the respective features in tRPC and GraphQL-WS for context

• tRPC
  • Lazy Mode - https://trpc.io/docs/typedoc/react-query/index/interfaces/WebSocketClientOptions#lazy
  • Connection Params - https://trpc.io/docs/client/links/wsLink#authentication--connection-params
• GraphQL Websocket
  • Lazy Mode - https://the-guild.dev/graphql/ws/docs/client/interfaces/ClientOptions#lazy
  • Connection Params - https://the-guild.dev/graphql/ws/docs/client/interfaces/ClientOptions#connectionparams

[unnoq]

HI @bnussman,

1. oRPC does not support lazy mode yet, but it fairly easy to implement or you can extend your WebSocket instance to support it (maybe there already is existing npm package), if you have time please create an issue for it.

2. What about attach connectionParams into url like this:

const websocket = new WebSocket('ws://localhost:3000?connectionParams=????')

const link = new RPCLink({
  websocket
})

[bnussman]

Thanks for the reply.

I prefer to keep connection params out of the URL to keep them more hidden from logging and such.

[unnoq]

@bnussman or just create a dedicated procedure to handle authentication, you instantly invoke it on connection

[unnoq]

I forgot about https://orpc.dev/docs/client/dynamic-link, you can easy implement lazy mode or wait until authentication finish.

[bnussman]

Got it. I'll take a look. Thank you!