dweetio node should send payload value only

[node-red]

dweetio node should send payload value only

[dceejay]

Matt,
the dweetio API only allows the sending of objects... - so raw values have to be wrapped in something to make it an object.... - we chose "payload" .... if a node-red dweetio input node receives an object called payload then it does "do the right thing" and unpacks it back to a raw value.

Closing this as would need them to change their API to allow sending raw data.

[mattbrailsford]

But there should be an option to say "I'll make my own object so don't wrap
it in a payload object". I have another system connecting at the other end
for which it expects the dweet contents to be a specific format, if I want
to connect it to node-red, I now have to explicitly handle the payload
object and unwrap it, which isn't ideal.
On 9 Jul 2015 10:39 pm, "Dave Conway-Jones" [email protected]
wrote:

Matt,
the dweetio API only allows the sending of objects... - so raw values have
to be wrapped in something to make it an object.... - we chose "payload"
.... if a node-red dweetio input node receives an object called payload
then it does "do the right thing" and unpacks it back to a raw value.

Closing this as would need them to change their API to allow sending raw
data.

—
Reply to this email directly or view it on GitHub
#122 (comment)
.

[dceejay]

Whoa... you are so right.. now checks if it's an object and if so leaves it alone... otherwise wraps it in {payload:...

republished (so leaving closed)

[mattbrailsford]

Perfect! :)
On 9 Jul 2015 11:21 pm, "Dave Conway-Jones" [email protected]
wrote:

Whoa... you are so right.. now checks if it's an object and if so leaves
it alone... otherwise wraps it in {payload:...

republished (so leaving closed)

—
Reply to this email directly or view it on GitHub
#122 (comment)
.