Edi condition stacking behavior

Stacked conditions are stacked using the Boolean AND operator. This introduces a breaking change. Fixes #83

Introducing EdiAnyAttribute.

This attribute changes the default condition stacking behavior from All conditions must be satisfied
to Any condition satisfied

Auto EndSegment Groups setting

Add code to automatically end segment groups when a non-matching segment is found. Fixes #75 (#76)
* Add code to automatically end segment groups when a non-matching segment is found
* Do not require standard headers/trailers to be modelled explicitly

field length update

Picture parse now supports field lengths greater than 255 characters (ushort precision)
Fixes #70

EdiTextReader does not Trim whitespace from component values

Fixes #53

Structural segments can also mark a separate segment-class

Structural segments can also mark a separate segment-class and their structural container.
This allows for a Message decorated class to have its Header and Footer fields grouped.

Closes #45

ReaderCache & the value binding bug

fixes ReaderCache & the value binding bug #42 .

EdiConditionAttribute. New functionality as well as an extensibility point.

Allow EdiConditionAttribute to stack that will then be checked with the OR logical operator. Added new functionality as well as an extensibility point for the condition attribute.
new features include

  1. Condition attribute stacking.
  2. Condition check for multiple values
  3. "CheckFor" toggle that switches between equal/Notequal check

Also now the condition attribute can be extended.

Bug fix for Functional Group Trailer values

Minor update. Bug fix in deserialization of the Functional Group Trailer

Integers & the Z padding

Minor release.
Now when we got an integer decorated with the 9(3) picture it is padded with zeros 0 instead of Z. Affects only writing back to EDI.

Edi Serialization

EDI serialization from CLR pocos is now supported.

Sample code:

var interchange = new MyInterchangeClass() {

     // fill the properties
     .... 
};
var grammar = EdiGrammar.NewEdiFact();
var output = new StringBuilder();
using (var writer = new EdiTextWriter(new StringWriter(output), grammar)) 
     new EdiSerializer().Serialize(writer, interchange);
}