Returning an array as a value causes {"undefined":{"$type":"atom"}} in result

[mik01aj]

Originally reported in Netflix/falcor#732.

---

Let say my route handler returns this:

{ path: ['things', thingId, 'linkedTopic'], value: ['topics', 123] }

Maybe you noticed - I forgot to wrap my value in Model.ref.

The returned result, when asking for ["things", 629026273, "linkedTopic", "headline"] is:

{"jsonGraph":{"things":{"629026273":{"linkedTopic":
    {"undefined":{"$type":"atom"}, "headline":{"$type":"atom"}}
}}}}

Definitely looks like a bug. 🪲

AFAIK returning arrays as results doesn't make any sense in Falcor (unless wrapped in ref or atom), so I guess you could just throw a meaningful error if there's an array returned as value.

The point is, returning array in place of a value doesn't make any sense (AFAIK), so Falcor should throw an Error instead of constructing weird objects with {"undefined":{"$type":"atom"}}. I never asked for key "undefined", so why do I get it in result? 🪲