Hey, if you're looking at the second argument of the dispatcher binding, that should just be an empt
Hey, if you're looking at the second argument of the dispatcher binding, that should just be an empty object - it's some internal thing apparently, which (in my opinion) should have never been exposed.
The way to pass custom arguments is to take advantage of RPC, which is supported by wfp. Your user worker can be an RPC entrypoint, just like your workers, and then you can pass in any arguments just like with normal bindings.
There's a special one for outbound workers, but that data isn't exposed to the user worker, as the goal of that is to pass trusted data around
The way to pass custom arguments is to take advantage of RPC, which is supported by wfp. Your user worker can be an RPC entrypoint, just like your workers, and then you can pass in any arguments just like with normal bindings.
There's a special one for outbound workers, but that data isn't exposed to the user worker, as the goal of that is to pass trusted data around
