A (very) simple parser/(des)erializer for Dot Notation text strings. It can deserialize text into strongly typed classes and/or dictionaries+lists.
In the remote possibility that you ever wanted to parse strings like these...
Network.DefaultInterface=eth2
Network.Domain=dauha
Network.Hostname=BSC
WLan.eth2.Network.DefaultGateway=192.168.0.1
WLan.eth2.Network.DhcpEnable=true
WLan.eth2.Network.DnsServers[0]=192.168.0.1
WLan.eth2.Network.DnsServers[1]=0.0.0.0
WLan.eth2.Network.SubnetMask=255.255.255.0
WLan.eth2.SSID=loudenvier
PictureHttpUpload.Enable=true
PictureHttpUpload.UploadServerList[0].Address=192.168.1.225
PictureHttpUpload.UploadServerList[0].Port=7000...into strongly typed objects as follows...
public record NetworkConfig(NetworkInfo Network, WLan WLan);
public record NetworkInfo(string DefaultInterface, string Domain, string Hostname);
public record WLan(NetworkInterface eth2);
public record NetworkInterface(Network Network, string SSID);
public record Network(string DefaultGateway, bool DhcpEnable, string[] DnsServers, string SubnetMask);...this library is for you!
With it all you need to do to deserialize the above text into these objects is:
var netConfig = DotNotation.Deserialize<NetworkConfig>(textInDotNotation);
Assert.NotNull(netConfig);
Assert.Equal("0.0.0.0", netConfig.WLan.eth2.Network.DnsServers[1]);
...Dahua's camera API/SDK uses this flavor of dot notation profusely in their responses (notice the entry Network.Domain=dauha in the example above). This library was born when I started writing code to inferface with a brazilian branded (Intelbras) Dahua facial recognition device. I adamantly refused to work with plain strings or untyped dictionaries, so I wrote a very simple dot notation parser and hacked my way with Newtonsoft's Json.Net to build strongly typed objects out of parsed dictionaries and lists.
Since Json itself is built as a collection of name/value pairs (dictionaries) and ordered lists of values (lists) it can be represented as a hierarchy of dictionaries (IDictionary<string, object>) and lists (IList<object?>), and the library simply parses the dot notation text into such hierarchy, then uses Json.Net to serialize it to Json and finally deserializes it back into strongly typed objects. Deserialization is totally optional, and you can work directly with the dictionary/list hierarchy, which can be useful for dynamic scenarios. You can also leverage the fact that the ExpandoObject implements the IDictionary<string, object> interface and pass it as the root of the Parse(string text, IDictionary<string, object> root) method and have proper dynamic access to parsed properties and lists.
Parsing is at the core of NetDot's functionality. You can use DotNotation.Parse() static method directly to parse dot notation text into a hierarchy of dictionaries and lists which can be traversed with some typecasting. Working with it can be a little awkward, so the best thing to do is to deserialize the text into strongly typed objects with DotNotation.Deserialize<T>()static method. You can also serialize objects to dot notation format (with many custom settings available to control de final output!) by calling DotNotation.Serialize() static method.
DotNotation.Parse will build a hierarchy of dictionaries and lists which can be traversed with some typecasting:
var dict = DotNotation.Parse("""
person.name=felipe
person.age=47
""");
var person = (Dictionary<string, object>)dict["person"];
Assert.Equal("felipe", person["name"]);
Assert.Equal("47", person["age"]);Simple members at root level are directly accessible (making it easy to parse lines of {name}={value} pairs):
var dict = DotNotation.Parse("""
person=felipe
age=47
""");
Assert.Equal("felipe", dict["person"]);
Assert.Equal("47", dict["age"]);Arrays will become lists holding either direct values or nested dictionaries for complex objects:
var dict = DotNotation.Parse("person[0]=felipe");
var people = (List<object?>)dict["person"];
Assert.Single(people);
Assert.Equal("felipe", people[0]); // holds a simple valuevar dict = DotNotation.Parse("person[0].name=felipe");
var people = dict["pessoa"] as List<object?>;
Assert.Single(people);
var person = people[0] as Dictionary<string, object>; // holds a nested Dictionary<string, object>
Assert.Single(person);
Assert.Equal("felipe", person["name"]); Arrays can hold other arrays (which could also hold arrays ad aeternum):
var dict = DotNotation.Parse("""
person[0].course[0]=judo
person[0].name=felipe
""");
var people = dict["person"] as List<object?>;
var felipe = people[0] as Dictionary<string, object>;
var courses = felipe["course"] as List<object?>;
Assert.Single(courses);
Assert.Equal("judo", courses[0]);Arrays can be defined with arbitrary indexes and the library will "fill" missing indexes in their backing lists with null values:
var dict = DotNotation.Parse("person[2]=felipe");
var people = dict["person"] as List<object?>;
Assert.Equal(3, people.Count);
Assert.Null(people[0]);
Assert.Null(people[1]);
Assert.Equal("felipe", people[2]);Deserialization works by first parsing the dot notation text into NetDot's customary hierarchy, then serializing it to JSON via Json.NET and, finally, deserializing the resulting JSON back into the proper type (again with Json.NET). This way the library leverages all amenities provided by Newtonsoft's amazingly robust, flexible and mature codebase. It works because Json itself is built as a collection of name/value pairs (dictionaries) and ordered lists of values (lists), which are incidentally equivalent to NetDot's parsed results.
To deserialize a simple class Person:
public class Person
{
public string Name { get; set; } = "";
public int Age { get; set; }
}Just call DotNotation.Deserialize<Person>(text):
var person = DotNotation.Deserialize<Person>("""
name=felipe
age=47
""");
Assert.Equal("felipe", person.Name);
Assert.Equal(47, person.Age);Notice that Json.NET took care of matching our pascal case properties to the lowercase keys used in this dot notation text, and that it also converted "47" to int. It will always try to convert "string" values in dot notation into the type of the matching property.
Records can also be deserialized as expected:
public record PersonRecord(string Name, int Age);
var person = DotNotation.Deserialize<PersonRecord>("""
name=felipe
age=47
""");
Assert.Equal("felipe", person.Name);
Assert.Equal(47, person.Age);Classes can be nested and have arrays/lists as members:
public class Master {
public string Name { get; set; }
public Detail[] Details { get; set; }
}
public class Detail {
public int Id { get; set; }
public string Tag { get; set; }
}var master = DotNotation.Deserialize<Master>("""
Name=Master Record
details[0].Id=123
details[0].Tag=test
details[2].Id=321
""");
Assert.NotNull(master);
Assert.Equal("Master Record", master.Name);
Assert.Equal(3, master.Details.Length); // one "missing" item was added to "fill" the list
Assert.Equal(123, master.Details[0].Id);
Assert.Equal("test", master.Details[0].Tag);
Assert.Null(master.Details[1]); // index 1 was missing so it was "filled" with null
Assert.Equal(321, master.Details[2].Id);
Assert.Null(master.Details[2].Tag);The previous code would work with no changes if Master and Detail were records:
public record Master(string Name, Detail[] Details);
public record Detail(int Id, string Tag);The library didn't start with serializion in mind, but now it's a first class citizen and it's surprizingly useful. For example, you can tweak it's options to serialize a class into an URL's query string.
NetDot serializes objects in dot notation format (the 'dot' connector is configurable) separating each entry by new lines (the 'entry separator' is also configurable):
var text = DotNotation.Serialize(new { Name = "Felipe", Age = 47 });
Assert.Equal("""
Name=Felipe
Age=47
""",
text);You can serialize very complex object graphs to dot notation with the same method:
record Person(string Name, int Age);
record Group(Person[] Persons);
record Job(string Name, decimal rate);
record Employee(
string Name, int Age,
Group Friends,
Group ManagedPeople,
Group Supervisors,
Job[] Jobs,
Dictionary<string, Job> JobTransfers) : Person(Name, Age);
var person1 = new Person("Ricardo", 45);
var person2 = new Person("Paulo", 72);
var person3 = new Person("Marcelle", 52);
var employee = new Employee(
Name: "Felipe",
Age: 47,
Friends: new Group(new[] { person1, person3 }),
ManagedPeople: new Group(new[] { person2 }),
Supervisors: new Group(new[] { person3 }),
Jobs: new[] { new Job("Worker", 20m), new Job("Slave", 1m) },
JobTransfers: new() {
["Night"] = new Job("Bouncer", 15m),
}
);
var text = DotNotation.Serialize(employee);
Assert.Equal("""
Friends.Persons[0].Name=Ricardo
Friends.Persons[0].Age=45
Friends.Persons[1].Name=Marcelle
Friends.Persons[1].Age=52
ManagedPeople.Persons[0].Name=Paulo
ManagedPeople.Persons[0].Age=72
Supervisors.Persons[0].Name=Marcelle
Supervisors.Persons[0].Age=52
Jobs[0].Name=Worker
Jobs[0].rate=20
Jobs[1].Name=Slave
Jobs[1].rate=1
JobTransfers[Night].Name=Bouncer
JobTransfers[Night].rate=15
Name=Felipe
Age=47
""", text);The DotNotationSettings class can be used to control serialization behavior. You can change many aspects of it such as which character to use as name/value separator (defaults to =), if spaces (or other filling characaters) are to be added after the name and/or before the value, if strings or all types should be quoted, which quoting character to use... even the . character itself can be changed to any other char. You can also define which Culture and date format to use for value serialization, determine if entries should be URL Encoded, among many other options.
var queryString = DotNotation.Serialize(new {
page = 10,
pageSize = 50,
user = new { id = 1, },
token = "my token/123"
}, settings: new () {
UrlEncode = true,
EntrySeparator = "&",
});
Assert.Equal("page=10&pageSize=50&user.id=1&token=my%20token%2F123", queryString);To make your life easier you can use the neat AsQueryString() extension method:
var queryString = new {
page = 10,
pageSize = 50,
user = new { id = 1, },
token = "my token/123"
}.AsQueryString();
Assert.Equal("page=10&pageSize=50&user.id=1&token=my%20token%2F123", queryString);