Google Git Google Git
Sign in
fuchsia/third_party/github.com/project-chip/zap/refs/heads/main
commit
65b23422e6007fa547bdf7b6813bd3c76e7c1f48
[log]
author
Bharat Raju <brdandu@silabs.com>
Tue Oct 13 13:35:39 2026 -0400
committer
GitHub <noreply@github.com>
Tue Oct 13 13:35:39 2026 -0400
tree
cfa211c091964412555ea6146173aa2d7350fa1a
parent
d2cf6ce46dd51f74f23416051aed8c6c07732674 [diff] 
fix(husky): make pre-commit work from GUI git clients (#1740)

GUI clients such as Sourcetree launch git without a full shell PATH, so
npx was not found and the pre-commit hook failed. npm install now writes
~/.config/husky/init.sh (Husky v9 sources it before every hook) using the
node that ran the install, so each developer gets the right path without
committing machine-specific setup. Drop the deprecated husky.sh source
line, which fails in Husky v10.

Also record Rollup's optional platform binaries in package-lock.json so
npm 11 (Node 24) can run npm ci against a lockfile last written by npm 10.

- JIRA: ZAPP-1779
5 files changed
tree: cfa211c091964412555ea6146173aa2d7350fa1a
  1. .cursor/
  2. .github/
  3. .husky/
  4. cypress/
  5. docs/
  6. public/
  7. resource-build/
  8. src/
  9. src-electron/
  10. src-script/
  11. src-shared/
  12. test/
  13. zcl-builtin/
  14. .editorconfig
  15. .eslintignore
  16. .eslintrc.js
  17. .gitignore
  18. .gitmodules
  19. .postcssrc.js
  20. .prettierrc
  21. .stylintrc
  22. apack.json
  23. babel.config.js
  24. cypress.config.js
  25. Jenkinsfile
  26. jest.config.js
  27. jsconfig.json
  28. LICENSE.txt
  29. package-lock.json
  30. package.json
  31. quasar.conf.js
  32. quasar.extensions.json
  33. quasar.testing.json
  34. README.md
  35. sonar-project.properties
  36. tsconfig.json
  37. zap-schema.dot
  38. 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