Releases: project-chip/alchemy
Releases · project-chip/alchemy
v1.5.40
v1.5.39
Features:
- Adds support for
Condition Requirements on Composing Device Types
section, and Data Model XML generation thereof - Supports generating XML for super set devices of devices without IDs
- Ignores rows which span all columns when parsing tables, as these are typically sub-headings
Fixes:
- "NULL" is no longer interpreted as an identifier in conformance
v1.5.38
v1.5.37
v1.5.36
v1.5.35
Fixes:
- Restored the "optional" tag to ZAP XML generation, as its absence was breaking linting
- Fixed a typo in test plan generation templates
- Composed device type requirements are now processed in a second pass, to avoid dependency ordering problems
v1.5.34
v1.5.33
v1.5.30
Fixes:
- Error when xref starts on new line; this is a band-aid until I can look into why the parser thinks this is a block element
- Elements with a Path field were not getting position set correctly, so error messages did not contain the source of the error
v1.5.29
Features:
- Alchemy-db now indexes namespaces, tags and device type composition
- Support for Element Requirements on Composing Device Types section
- Data Model XML now renders math expressions as element
- Data model conformance now notes if an element is from a different cluster
Fixes:
- Reworked conformance checking for matter-devices.xml generation to be more accurate, based on expressing a confidence in a conformance state evaluation (e.g. "[Condition]" will return as "possibly optional")
- Enums and bitmaps in ZAP XML no longer get redundant min/max values
Full Changelog: v1.5.27...v.1.5.29