Google Git
Sign in
fuchsia/third_party/github.com/project-chip/zap/74eadd0e9256ac2f411bbe02421cfe7d6ac43107
commit
74eadd0e9256ac2f411bbe02421cfe7d6ac43107
[log]
author
Bharat Raju <brdandu@silabs.com>
Mon Apr 14 08:51:53 2025 -0400
committer
GitHub <noreply@github.com>
Mon Apr 14 08:51:53 2025 -0400
tree
b0ba74ae99643343e09f26b7763b387c37ca979a
parent
e40b09d63affc19754fbc532079888b8e7ad46af [diff]
Fix the Legal Clusters view where users will only see clusters associated with a device type and not just enabled clusters which is wrong (#1573)

- Use the device types on the selected endpoint to figure out the device type clusters and then only show those clusters in the UI.
- The Legal clusters UI view will also not allow users to enable/disable non compliant clusters and also not show non compliant clusters.
- Adding cypress tests for filters of legal and enabled clusters
- Add more tests where the clusters are check for enablement when clicking on the client and server checkboxes
- Github: ZAP#316
13 files changed
tree: b0ba74ae99643343e09f26b7763b387c37ca979a
  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