Google Git
Sign in
fuchsia/third_party/github.com/project-chip/zap/aa683833f1025869ede994928e7d1a0e1a4d7269
commit
aa683833f1025869ede994928e7d1a0e1a4d7269
[log] [tgz]
author
Bharat Raju <brdandu@silabs.com>
Thu Nov 13 22:33:04 2025 +0530
committer
GitHub <noreply@github.com>
Thu Nov 13 22:33:04 2025 +0530
tree
226341ba48e69277535d8a86916c731a4ae60c86
parent
5adfdc84d86d42fb554c419d93a2c6ebf4bacf98 [diff]
Changing the data type by name helpers to use data type name and cluster (#1669)

- Updating types.getSignAndSizeOfZclType to types.getSignAndSizeOfZclTypeAndClusterId for better accuracy and avoiding duplicate data types across clusters.
- updating the code associated with the above as required in the code.
- deprecating as_bytes and data_types_for_enum as they are no longer used.

- Handling clusterId for all the helpers. Now the helpers can mention clusterId=ID-NUMBER along with the helpers in .zapt templates to account for the helpers. The helpers in helpers.js files now extract this from the this object automatically

- Updating the feature level of zap

- Adding unit tests for the as_underlying_zcl_type helper with cluster Id reference
- Github: ZAP #1592
18 files changed
tree: 226341ba48e69277535d8a86916c731a4ae60c86
  1. .github/
  2. .husky/
  3. cypress/
  4. docs/
  5. public/
  6. resource-build/
  7. src/
  8. src-electron/
  9. src-script/
  10. src-shared/
  11. test/
  12. zcl-builtin/
  13. .editorconfig
  14. .eslintignore
  15. .eslintrc.js
  16. .gitignore
  17. .gitmodules
  18. .postcssrc.js
  19. .prettierrc
  20. .stylintrc
  21. apack.json
  22. babel.config.js
  23. cypress.config.js
  24. Jenkinsfile
  25. jest.config.js
  26. jsconfig.json
  27. LICENSE.txt
  28. package-lock.json
  29. package.json
  30. quasar.conf.js
  31. quasar.extensions.json
  32. quasar.testing.json
  33. README.md
  34. sonar-project.properties
  35. tsconfig.json
  36. zap-schema.dot
  37. zap-schema.svg
README.md

ZCL Advanced Platform

ZCL Advanced Platform

Build and release packages Zigbee code regeneration Matter code regeneration

What is ZAP?

ZAP is a generic generation engine and user interface for applications and libraries based on Zigbee Cluster Library, the specification developed by the Connectivity Standards Alliance.

ZAP allows you to perform the following:

  • perform SDK-specific customized generation of all global artifacts (constants, types, IDs, etc) based on the ZCL specification
  • provide UI for the end-user to select specific application configuration (clusters, attributes, commands, etc.)
  • perform SDK-specific customized generation of all user selected configuration artifacts (application configuration, endpoint configuration, etc) based on ZCL specification and customer-provided application configuration.

ZAP is a generic templating engine. Examples are provided for how to generate artifacts for the C language environment, but one could easily add new templates for other language environments, such as C++, java, node.js, python or any other.

Quick setup

Refer to Setup Instructions

Source code

Refer to development instructions for more details.

License

This software is licensed under Apache 2.0 license.

Usage Documentation

Detailed Developer Documentation