search

Steveorevo / node-red-contrib-actionflows

Provides a set of nodes to enable an extendable design pattern for flows.
45 stars 12 forks source link

TypeError: prop.indexOf is not a function #17

Closed travis-icorein closed 3 years ago

travis-icorein commented 3 years ago

The debug panel is showing an error from the action node in my tab/flow. I can't figured out what is causing it.

The actionflow appears to execute once, as I have a function node following the action in node, and a debug node following the function node. The debug node shows the msg object from the first instance/iteration (the function following action in seems to go as expected). I am guessing that the error happens on the second iteration. However, as stated, the error reported is from the action node.

Any ideas how I can troubleshoot this and determine what is causing it to break?

I have another tab, using the same paradigm/pattern (ensures that client npm objects are initialized to connect to databases). It is working fine without issue (which makes it especially confusing as to determining the cause).

travis-icorein commented 3 years ago

Never mind, I found the bug in my function node (by iteratively isolating running code until the bug would manifest, or not). It stemmed from assigning a msg.obj to a boolean rather than a string (essentially). Leaving this in case it helps anyone else.