Weird JSONata problem

[cymplecy]

@knolleary

Unfortunately, this is a limitation of JSONata.

and

@ghayne

it's just funny that my original flow stopped working after moving from 0.18.4 to 0.19.1.

My understanding (which may be wrong) is that NodeRED hooks in somehow to JSONata as it has payload and flowContext NodeRED specific syntax

And @ghayne says it used to be able to access buffer values using the old NodeRED syntax of payload.x in 0.18.4

So, if it used to be able to do it - is it possible to do it now again e.g get at individual bytes within he buffer object and return them to the JSONata engine as integers (or whatever they were returned as in 0.18.4)

if so, could we look thru the code history and try and come up with a pull-request to restore it?

Simon

[knolleary]

Having dug into it, this was a change introduced in JSONata 1.5.2 - https://github.com/jsonata-js/jsonata/issues/147

A consequence of that fix is that payload.1 doesn't work but payload."1" does.

Will discuss with Andy on the JSONata project.

[ghayne]

Thanks Nick,
Works!