Vanilla Client: error deserializing procedure arguments

[v-morlock]

When using the Vanilla client ("@rspc/client": "0.1.3",) to call this mutation on the currently published server (rspc = { version = "0.1.3", features = ["axum"] }
specta = { version = "1.0.5", features = ["chrono"] }
):

        .mutation("myprocedure", |t| {
            t(|s, _: ()| {
( ...)
            })
        })

like this:

	import { createClient, FetchTransport } from '@rspc/client';
	import type { Procedures } from '../../../../../../../../controls-rs/rspc.schema';
	const client = createClient<Procedures>({
		transport: new FetchTransport('http://localhost:4000/rspc'),
	});

client.mutation(['myprocedure'])

rspc returns this error:

{
    "jsonrpc": "2.0",
    "id": null,
    "result": {
        "type": "error",
        "data": {
            "code": 400,
            "message": "error deserializing procedure arguments",
            "data": null
        }
    }
}

I could reproduce the same behaviour with 1.0.0-rc.3. I guess the issue is that the vanilla client sends {} as request... Any ideas how to work around this or what a possible fix could look like? I'd be happy to submit a PR but could use some pointers on where to look for a solution

[cfmatthee]

Observed the same problem. A mutation without any arguments does not know what to do with the {} argument forwarded from the vanilla client. Turning tracing on showed that this is considered a Map.

Switching to the WebSocketTransport made the problem go away. Alternatively, adding a HashMap argument to the function call also made the problem go away. Not a fix. More of a hack until the real source of the problem can be located and fixed.