Shadow.Quack 2.0.3

Shadow Quack

This package allows the easy population of values directly from an existing object or dynamic to a dynamically implemented immutable interface it also allow the merge of several objects or dynamic retuning a new object.

Though it is possible to use interfaces with both getters and setters the intent is for interfaces with get-only properties making the contract immutable.

The combination of these two functions makes an interface the only required data contract. The merge functionality allows for functional operations to return an new object with the values from one or more source. The use of a dynamic in this context allows for the simple overriding of one or more properties. The resulting new object has the new property values set with the remaining properties carrying the values through from the source.

There are also many abstraction applications where being able to Duck Type data to an interface from an object outside of your control turns out to be very useful.

Duck.Implement<T>()

public interface IData
{
    int Property1 { get; }
    string Property2 { get; }
}

var data = Duck.Implement<IData>(new
 {
     Property1 = 100,
     Property2 = "This"
 });        

Duck.Merge<T>()

var data = Duck.Implement<IData>(new
 {
     Property1 = 100,
     Property2 = "This"
 });
 var merged = Duck.Merge<IData>(data, new {Property2 = "That"});

This results in Property1 = 100, and Property2 = "That", this is useful if you want to take an existing object and just update one property, this creates a new object keeping the immutability of the original source. You can merge several objects on a last one wins basis.

var data = Duck.Implement<IData>(new
 {
     Property1 = 100,
     Property2 = "This"
 });
 var merged = Duck.Merge<IData>(data, 
     new { Property2 = "That" }, 
     new { Property1 = 35 }, 
     new { Property2 = "Other" });

This results in Property1 = 35, and Property2 = "Other"

IProxy

Shadow Quack also allows extension via Proxy types, this is done via an IProxy interface and a custom Type and Property classes.

The extensions written already, provided in separate packages, include;

• Shadow Quack JSON
• Shadow Quack CSV
• Shadow Quack XML
• Shadow Quack Args

There is also a further extension of this ecosystem in Quack API which includes custom implementation of JsonConverter and JsonConvertorFactory, that wrap the JSON proxy, to allow the use of Interfaces as return and parameter types in ASP .Net API calls.