Releases: project-chip/alchemy
Releases · project-chip/alchemy
v0.9.7
v0.9.6
Features:
- Support for
:alchemy-escape:
attribute entry, which disables all alchemy processing until it is unset (or the end of the file) - Disco: New
removeMandatoryFallbacks
option, which removes fallbacks from fields marked pure mandatory - Disco: The Default column is automatically renamed to Fallback
- Disco: References to data types inside of tables are given a label when
normalizeAnchors
is enabled
Fixes:
- Conformance: Comparison expressions can now nest inside logical expressions, e.g.
(SomeAttribute < 0) & (SomeOtherAttribute > 0)
- Disco: Unrecognized columns now appear in their original order when a table's column order is normalized
v0.9.5
Features:
- New
--normalizeAnchors
flag ondisco
to remove anchor labels, and patch up stuttering references - Support for reading (without parsing) spec docs with include directives mid-table (lookin' at you, OperationalState)
Fixes:
- Stable ordering of conformance elements in ZAP XML
- Descriptions are no longer truncated by fake-out sentence-enders "i.e." or "e.g."
v0.9.4
Features:
- Support for quality attributes in command and attribute elements in ZAP XML
- New
specOrder
flag onzap
command reorders ZAP XML to match order of declaration in the spec
Fixes:
- Suppressed several pointless warnings
- Alchemy commend in ZAP XML now alphabetizes document paths
v0.9.2
Features:
- Support for simple math equations in conformance (e.g. "AttributeName + 1 > 0")
- Support for null comparisons in conformance
- Add cluster-revisions table to alchemy-db
Fixes:
- Docs with a incorrect doc-type guess of "Cluster" no longer create empty cluster groups
v0.9.1
v0.9.0
Features:
- Reworked handling of matter-devices.xml to match approach agreed to with SDK team
- Mandatory Base Device Type requirements are no longer rendered unless overridden by a Device Type, or become Mandatory after evaluation
- Features no longer renders simple Mandatory conformance, leaving it implied
- Device Type typeNames are no longer prefixed with "Matter"
- Device Type names are now more consistent in separator use (e.g. "MA-extended-color-light" instead of "MA-extendedcolorlight")
- Support for new Device Type Requirements section
- Experimental: testplan command allows generating a basic test plan for a cluster
- Experimental: yaml2python command converts a YAML test file to its Python equivalent
Fixes:
- Windows grammar no longer chokes on "\r\n"
- PICS conformance now supports "|" as well as "||"
- Invalid conformances now issue warning when building spec
- ZAP Namespaces are now inserted in alphabetical order
- Spec building now probes the document to guess doc type when the path is not sufficient
- Duplicate Device Type IDs now issues a warning
- Cluster IDs set to "TBD-ID" now issue a warning while generating code
- Cluster Groups can now specify individual test plan override paths per cluster
- Enums and Bitmaps which do not declare which base type they inherit from now issues a warning
v0.8.4
v0.8.3
Features:
- Support for "Cameras" domain
Fixes:
- Drops "reportable" attribute whenever found in ZAP XML
- Cluster conformance in Data Model is no longer rendered if it's straight mandatory
- Generating matter-devices.xml for a subset of device types no longer deletes all other device types (sorry Sergio)
v0.8.2
Features:
- Support for comparisons in conformance, e.g. "AttributeValue < 5"
- Experimental conformanceXML flag for ZAP generation which embeds conformance information in attributes, commands and events
Fixes:
- Data model generation now generates quieterReporting, diagnostics and sourceAttribution qualities
- Data model PICS codes for base clusters no longer clobber PICS code on aliased clusters