AleksLitynski/teller

print_known no longer works

Opened this issue · 1 comments

Something I think has changed so that player no longer has nodes connected via knows_of. When the query is run and player is retrieved (as node), it accurately returns node.get_value("named") as player, but returns node.get_values("knows_of") as None. Looking in the visualizer at a query generated for get_node_by_name("player") (via describe_noun) at a depth of 2, I see a cloud of larger green nodes with no name attached. I am not exactly sure how to interpret that data.
Basically, it appears that something, either in the demo or database or generation code, has created some kind of a disconnect between the player and the known nodes, and it is stopping us from printing room contents. This is worrying, because knows_of functions very similarly to how we would then implement has for inventory management, blocking us from moving forward on picking up and putting down objects.

If we switch the query from "knows_of" to "know_of" (inspired by an item labeled so in the graph) the query returns four nodes named "does".

{"type": "get", "params": {"depth":1}, "search": {"edges": [{"direction": "inbound","type": 
"describes","weight-time": "1","terminal": {"type": "relationship","edges": [{"terminal": {"type": "type","value": "named"}},{"terminal": {"type": "value","value": "player"}}]}}]}}

node.get_value("know_of"):does
print_known():a does, a does, a does, a does