You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I want to serialize a large tree of YamlNodes to a JSON string, but it seems that the Serializer either:
Outputs YAML instead of JSON when attempting to serialize a YamlNode
Outputs JSON with unexpected additional information ("RootNode" and "AllNodes") when attempting to serialize the same node wrapped in a YamlDocument
I want to manually create the node trees because of my game's structure. Creating serialized "proxy" objects feels like too much, but seems to be the only supported serialization route. I appreciate your help.
To Reproduce
The toy example below recreates both problems. For reference, I'm using version 15.1.1 binaries loaded into Unity. I first encountered the problem while using the Unity asset store package. I recently tried the binaries and still had the same problem.
YamlMappingNodenode=new YamlMappingNode(){{"ingredients",new YamlSequenceNode(){"sugar","water","purple"}}};YamlDocumentdoc=new YamlDocument(node);varserializer=new SerializerBuilder().JsonCompatible().Build();// Swap for Console.Write();
Debug.Log(serializer.Serialize(node));
Debug.Log(serializer.Serialize(doc));
The code above outputs the following to the console.
Describe the bug
I want to serialize a large tree of YamlNodes to a JSON string, but it seems that the Serializer either:
I want to manually create the node trees because of my game's structure. Creating serialized "proxy" objects feels like too much, but seems to be the only supported serialization route. I appreciate your help.
To Reproduce
The toy example below recreates both problems. For reference, I'm using version 15.1.1 binaries loaded into Unity. I first encountered the problem while using the Unity asset store package. I recently tried the binaries and still had the same problem.
The code above outputs the following to the console.
The text was updated successfully, but these errors were encountered: