Foursquare Node - recommended venues (return multiple results) about node-red-web-nodes

[knolleary]

For multiple messages, this description isn't what we discussed. I know there was some confusion over what we meant by multiple messages versus multiple results in a single message. And it is entirely possible the implementation in PR is more up to date than this... but need to clarify this first.

Here's what I would expect for the combinations of 'requested num of results' and 'single/multiple messages'

requested num of results=1 , single message

• The node sends a single message:node.send(msg)
• msg.payload set to the JSON representation of the venue
• msg.lat/lon/etc set to the relevant values for the venue
• msg.title set to something sensible

requested num of results=1 , multiple messages

• The node sends a single message:node.send(msg)
• msg.payload set to the JSON representation of the venue
• msg.location.lat/lon/etc set to the relevant values for the venue
• msg.title set to something sensible

requested num of results>1 , single message

• The node sends a single message:node.send(msg)
• msg.payload set to an array of objects, each of which has the properties:
  • payload set to the JSON rep of the venu
  • location.lat/long/etc etc set to the relevant values
  • title set to something sensible
• msg.lat/lon/etc left unset

requested num of results>1 , multiple messages

• The node sends a message for each result.
  This can either be achieved by calling node.send(msg) for each result in turn, or calling node.send([[result1,result2,result3,...]]) - note the double level of array for this to work.
  For each of the messages sent...
• result1.payload set to the JSON representation of the venue
• result1.location.lat/lon/etc set to the relevant values for the venue
• result1.title set to something sensible

[hbeeken]

In which case I "still" don't completely understand the multiple msgs thing as I thought I'd implemented/written down what we'd discussed :-) I'll look at it some more and see where my confusion lies.

BTW the info here is the same as in the PR so that needs updating too....

[hbeeken]

Implemented as per @knolleary comment. Pull request merged and closed. Therefore closing this issue.