Re: Unbelievable issue with accessing node as field of other node
Okay, after speaking with a roku guy, this does look like a bug.
I've tested a workaround.
if you have node fields, then add them as children also once you pass the thread boundary, remove the duplicate child - your node field will now work
I have an elegant way of doing this with a base contentnode class, which has nodeFieldNames array and hasNodeFields bool fields declared when I create my nodes in my background task, my node factory adds the contentnode fields as children, and sets the nodeFieldNames and hasNodeFields values via a WorkAroundNodeRendesvouBug method
on the other side, I then iterate over the node graph, and remove all children that correspond to contentNodeFields, on all nodes that have hasNodeFields set to true
I can do this easily and without much fuss becauseI have a framework for processing my json into nodes, and for returning my contentNodes back to RSG.
I can't share exact code, because it belongs to my client
Good luck peeps
George Cook https://linkedin.com/in/georgejecook/ Roku developers slack group (http://tiny.cc/nrdf0y) : georgejecook
Contact me on roku developer slack group, or via pm to discuss consultancy/work opportunities/rooibos unit testing framework