Skip to content

Releases: IP-XACT/XactFlow-design

v0.1.2

Choose a tag to compare

@mtravaillard mtravaillard released this 28 Oct 14:27

Add comment at the beginning of the generated xml files to says it was generated by this tool.
Workflow change due to ubuntu-latest update.
Small changes due to XactFlow v0.2.0 (elaborate renamed to link)

Full Changelog: v0.1.1...v0.1.2

v0.1.1

Choose a tag to compare

@mtravaillard mtravaillard released this 21 Oct 09:38

Fix #1

v0.1.0

Choose a tag to compare

@mtravaillard mtravaillard released this 30 Sep 08:45

First public release of xactflow-design, a
XactFlow exporter plugin that serializes an
ipxact.Design object into a valid IEEE 1685-2022 IP-XACT design XML
document.

What's included

  • A full writer covering every Design field: component instances, interconnections
    and monitor interconnections sharing one XML container, ad hoc connections,
    choices, parameters, and assertions, hand-rolled lxml.etree construction mirroring
    ipxact-compiler's parser structure in reverse.
  • DesignExporter, registered under the xactflow.exporters entry point, so
    it's discovered automatically as the xactflow design ... CLI subcommand
    once installed.
  • A test suite backed by the real schema: every generated document is
    validated against design.xsd with lxml.etree.XMLSchema, round-tripped
    through ipxact.parse_file for object equality, and checked with
    xactflow.SCR.run_single_doc_checks.
  • Required XSD cardinalities left unsatisfied raise a clear error naming
    what's missing, instead of producing schema-invalid XML: a second
    interconnection endpoint, an ad hoc connection's port references, a monitor
    interconnection's monitors, a power domain link's internal references, a
    choice's enumerations, and a part select's indices or range.

Status

This is an early, alpha-stage release, scoped to a bare-object serializer: given
an ipxact.Design, no elaboration, no multi-file resolution. Handling an
ElaboratedDesign (re-materializing a resolved multi-instance design back to
XML, or writing a matching designConfiguration alongside it) is a planned
later addition, not implemented yet. See the
README for
design notes, and for why xactflow design ... can't yet be driven end-to-end
from XactFlow's CLI without going through elaboration first.

License

LGPL-3.0. See LICENSE.

Full Changelog: https://github.com/IP-XACT/XactFlow-design/commits/v0.1.0