You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Both examples allow to reuse classes, but first one is clearer because it explicitly defines Segment property. It is also more intuitive for newcomers (i was bitten by it) than second form.
In general it could allow deeper type of "element" in outer one (like Segment or Element in SegmentGroup, but not SegmentGroup inside SegmentGroup).
This would change:
Classes that are decorated with Segment, SegmentGroup, Message, Group or Interchange consume the segment that defines the contrainer and cannot be reused inside them.
I'm not sure if it would break compatibility, but it should not.
The text was updated successfully, but these errors were encountered:
I would like to allow to use Segment or Element with same path as SegmentGroup - reconsider #32 or #36.
This would allow this class definition as:
instead of:
Both examples allow to reuse classes, but first one is clearer because it explicitly defines Segment property. It is also more intuitive for newcomers (i was bitten by it) than second form.
In general it could allow deeper type of "element" in outer one (like Segment or Element in SegmentGroup, but not SegmentGroup inside SegmentGroup).
This would change:
I'm not sure if it would break compatibility, but it should not.
The text was updated successfully, but these errors were encountered: