v0.7.1
Features:
- Errata file Alchemy now looks for a
.github/alchemy/errata.yaml
file relative to the root of the repo; this contains overrides for handling of spec parsing, disco-balling and ZAP template generation (the initial default file is in PR#10383; until that merges, Alchemy will use a default embedded errata file. - Global Objects in ZAP If Alchemy finds bitmaps, enums, structs, events or commands outside of a cluster definition, it will treat these as global objects; if they're referenced by any cluster during ZAP template generation, it will add them to
src/app/zap-templates/zcl/data-model/chip/global-bitmaps.xml
,global-enums.xml
,global-structs.xml
, etc. - Quality Verification Qualities are now checked against a set of valid qualities for their entity types, and a warning is issued if a quality is used for a nonsensical entity (e.g. Large Message on a Cluster)
Fixes:
- Clusters with TBD-IDs can generate ZAP templates
- The Disallow conformance is now allowed to follow non-qualified mandatory or optional conformances
- ZAP templates now support commandField requirements
- ZAP templates now support long_octet_string
- Data types with names containing spaces are now coerced into valid ZAP names
- Enum values lacking a name column are given names created from the summary or description columns
- Added endpoint and tag data types to ZAP generation