v0.19.0
What's Changed
For all versions <0.19 the AhbReader and MigReader omitted Segments in between <Uebertragungsdatei>
and <M_FORMAT>
where FORMAT
is e.g, 'MSCONS' or 'UTILMD'.
The effect was, that you couldn't find and UNA, UNB or UNZ segments in neither the MIG nor the AHB (see issue #57 where you also find examples.)
We decided against modeling the Übertragungsdatei as separate class and add an extra hierarchy layer to our data model because since some XML AHBs/MIGs do contain the extra layer and others don't this would overcomplicate things for consumers with only little added value. Instead the respective segments are appended to the elements
before/after the segments from inside the <M_FORMAT>
tag and have a boolean flag is_on_uebertragungsdatei_level
which indicates if they are located outside the <M_FORMAT>
tag (true
).
- feat: Support
<Uebertragungsdatei>
inMigReader
(adds flagis_on_uebertragungsdatei_level
to MIGSegment
model) by @hf-kklein in #133 - feat: Support
<Uebertragungsdatei>
inAhbReader
(adds flagis_on_uebertragungsdatei_level
to AHBSegment
model) by @hf-kklein in #132 - feat: Add
Segment.is_on_uebertragungsdatei_level
to AHB(esser) View (the aggregated instead of only the bare data model) by @hf-kklein in #134
Full Changelog: v0.18.1...v0.19.0