Support autogenerated values about edi.net HOT 3 CLOSED

Also A "Position/Index" is handy when inside the elements themselves.

from edi.net.

The attribute should also have a scope. Something like Container & Self. This will make a distinction when dealing lets say with structural segments like the Message trailer segment where where is need to present the segment count inside the parent container (The message) and not the self container (the segment)

from edi.net.

In the end I settled with EdiCountAttribute that counts controls. That is contextual numbers of Segments, Messages and Groups.
At the moment it is used only in the EdiWriter when serializing. (EdiReader does not do validation with se same mechanism, at least not yet)
If placed on a model value property alongside with the EdiValueAttribute it will override any existing value found in the model with the correct count from within the writer.

Some exmples fox X12 (same applies for EDIFact as well).

public class Interchange
{
 /* ... other properties ... */
        [EdiValue("9(1)", Path = "IEA/0", Description = "IEA01 - Num of Included Functional Grps")]
        [EdiCount(EdiCountScope.Groups)]
        public int GroupsCount { get; set; }
}

[EdiGroup]
public class FunctionalGroup
{
 /* ... other properties ... */
       [EdiValue("9(1)", Path = "GE/0", Description = "97 Number of Transaction Sets Included")]
       [EdiCount(EdiCountScope.Messages)]
       public int TransactionsCount { get; set; }
}

 [EdiMessage]
 public class Message
 {
 /* ... other properties ... */
       [EdiValue(Path = "SE/0", Description = "SE01 - Number of included segments")]
       [EdiCount(EdiCountScope.Segments)]
       public int SegmentsCount { get; set; }
}

from edi.net.