I have a bunch of lists and they contain null values which are very useful. A null means there is no information in that index but that in and of its self is information. Most nodes freak out when a null is passed through it. Can any one explain why this is?
I’ve already reported on this some time ago.
Unfortunately, there doesn’t seem to be any progress on this. I suggest you gather a list of affected nodes and post a new issue on GH.
I’d guess that the main reason for this is that someone was too lazy to add a check for null values.
You can also find a few nodes in spring nodes beginning with Null*, that try to circumvent some of the built-in node’s limitations.
