Access to actual JSON payload. about goworker HOT 5 OPEN

Currently, there's no way to access the JSON payload except through the args interface.

I am investigating a way to specify the type of object you want for a worker function. Possibly something along the lines of:

goworker.RegisterType("MyClass", myFunc, &MyType{})

where you would only do one type assertion within myFunc for args.(MyType).

Alternatively, we could use json.RawMessage and have the function do the unmarshalling, but this, too, would require some reworking. Possibly something along the lines of:

goworker.RegisterRaw("MyClass", myFunc)

then within the worker

var val MyType
json.Unmarshal(raw, val)

What would work better for you?

from goworker.

I suppose the RegisterRaw approach is a little more flexible (and relevant to my use-case). I have a nested map of arrays of maps. I was just thinking about using something like go-simplejson to unmarshal it, if access to raw JSON was there.

from goworker.

+1 for RegisterRaw

from goworker.

👍 As well. I think this will help with a lot of bigger payloads complex payloads.

My workaround was actually to just save a temp .json file, and have the goworker trigger a download from s3, and unmarshal it into a struct. Though hacky, cut down time on building lots of workers.

from goworker.

👍 on RegisterRaw. My workaround was to Marshal the payload back and then Unmarshal to my the actual struct, which is quite wasteful.

from goworker.