Addressable port in WirePattern behaves incorrectly when receiving IP from another component

[paulyoung]

The issue I'm seeing as that a packet sent from a component isn't being converted into an object with array indexes as keys.

I have a component which sends a string from its NAME out port to an addressable port on another component like so:

Create(CreateTask) NAME -> TASKS[0] List(ListTasks)

Here, data.tasks is My task in the WirePattern proc function.

However, passing a string identical to the one sent above produces the expected result:

'My task' -> TASKS[0] List(ListTasks)

data.tasks is { '0': 'My task' }

My tests for this component pass but they only send IIPs. I only saw the issue when sending an IP from another component when running a graph.

[trustmaster]

I haven't tested it with output from a component either, so it could be a bug indeed. Theoretically there should be no difference between an IIP and a normal IP.

[trustmaster]

I've added a test for this in Helpers spec (see link above) but it passes. Seems like it's something with the FBP parser or addressable ports in Networks.

[paulyoung]

Let me know if there's anything else I can do to help.

[trustmaster]

@paulyoung could you make a spec that reproduces this issue for you?

[paulyoung]

I wasn't sure where to start so just created a demo project that reproduces the issue for now.

[trustmaster]

@paulyoung thanks! That should be sufficient!

[bergie]

Fixed via the Process API port of WirePattern #526