Unjsonify Function about treelib HOT 3 CLOSED

We are collecting extra features based on the Tree object. A module located in treelib.plugins is added to hold these features. You can add your unjsonify() function there.

What do you mean about value in the json tree? At present, both node id and data are preserved in the json string. But treelib currently complains about the tuple key in your example, as the to_json function needs the key to be a string. We are glad if you can enhance it.

from treelib.

Just FYI, I just forked and created a pull request with the unjsonify code in my original post.

Hmm. I'm not actually quite sure what you mean. It seems to me that when I parse through the JSON string, I only see the keys for the JSON string. Could you provide a small example of a JSON string that contains both the key and value for each node?

Also, why do the keys added to the tree need to be a string? I've been using integers, tuples, and essentially any immutable value as keys, and the tree has always built successfully.

Sorry for the late response!

from treelib.

This issue is included in this one: #85 (json/yaml serialization/deserialization)

from treelib.