var model = new Model(); var pavel = new Employee("Pavel"); model.Companies.Add(new Company("Boldbrick & co.") { Departments = new List<Department> { new Department("Software & Visions", "swv") { Teams = new List<Team> { new Team("Visions") { Employees = new List<Employee> { // I was forced to move // pavel variable declaration completely out of scope pavel, new Employee("Ondra"), }, IsAwesome = true, }, new Team("Developers") { Employees = new List<Employee> ( // I can't do any statements or declarations here // to prepare my data in-place devNames.Select(n=>new Employee(n)) ) { // note I can't add pavel first pavel, } } } } } });But there are downsides with approach above. You can't easily add same instance into 2 nodes. It forces you to declare pavel variable completely out of scope. And you can't use statements to prepare your data in place either. Note how Pavel is inserted after other employees into Developers team. The LINQ Select() helped great deal here, but it's not always possible to use it. With more complex model and bigger tree to build, this will become unmanageable mess.
So, extension methods and lambdas to rescue. Do you like code below better ? I certainly do. I can use statements and variable declarations in inner scope. I get more dense and readable code.
var model = new Model(); model.AddCompany("Boldbrick & co.", bb => { bb.AddDepartment("Software & Visions", "swv", swv => { // variable is still bit out of scope, but not in the root scope var pavel = new Employee("Pavel"); swv.AddTeam("Visions", visions => { visions.AddEmployee(pavel); visions.AddEmployee("Ondra"); visions.IsAwesome = true; }); swv.AddTeam("Developers", devs => { devs.AddEmployee(pavel); // I can add more employees after Pavel devs.AddEmployees(devNames.Select(n => new Employee(n)), dev=> { dev.Age = 33; }); // and also can use any complex statement in-place for (int i = 0; i < devNames.Count; i++) { int ix=i; devs.AddEmployee(devNames[i], dev => { dev.Age = ix; }); } }); }); );});
How the extension method looks like ?
Below is extension method over external structure Department, which accepts same parameters as Team constructor. Inside is instance creations and adding to the collection. Finally to allow the nesting of scopes, we pass the new instance to Action<> delegate.static public Team AddTeam(this Department self, string name, Action<Team> result = null) { var item = new Team(name); self.Teams.Add(item); if (result != null) result(item); return item; }
Generate the extensions
The extension method above is nice and useful but it's quite boring to write it for each combination of container and child item. Multiplied by all constructor signatures. So I decided to create ReflectionFluentator which can generate the code for you. It reads your model via reflection and generates the C# extensions. See sample how to use the generator.And the same thing for XML ? Sure. You provide the XSD to XsdFluentator. See sample how to use the generator.
var doc=new XDocument(); doc.AddLibrary("Prague",prague => { prague.AddBook("Saturnin", book => { book.AddAuthor("Zdenek Jirotka"); }); prague.AddBook("Bylo Nas 5", book => { book.AddAuthor("Karel Polacek"); }); });This code can generate this XML as expected.
<library id="Prague" xmlns="http://polyglottos.googlecode.com/svn/trunk/demomodel/library.xsd"> <book name="Saturnin"> <author name="Zdenek Jirotka" /> </book> <book name="Bylo Nas 5"> <author name="Karel Polacek" /> </book> </library>Note that both generators are more prototypes than ready to ship. They don't handle any edge scenarios when reading the metadata or writing the code. Fluentator is part of Polyglottos project. If you like the idea and wish to contribute improvements, please talk back.
At this point some of you may wonder what else could be made fluent this way. In my case, I realized that I need to generate the code and the code is just nested structure. So I created CodeDom code generator Polyglottos with fluent API. That's for another article next year. Enjoy the party tonight!
My Linkedin profile
