Allow cluster specific and generic data types with the same name in the XML (#1542) * Allow cluster specific and generic data types with the same name in the XML - This solves the issue of loading a same named generic and cluster specific data type. - The issue was with the generic data type type searches not checking if their cluster reference does not exist and thus getting the cluster specific data type instead. Now that check is added and duplicates issue is resolved - Ran into another ZAP generation issue while running zap_regen_all.py and fixed that error in helper.js - add tests for loading same named data types where one is generic and another is cluster specific - Github: ZAP#1540
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:
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.
Refer to Setup Instructions
Refer to development instructions for more details.
This software is licensed under Apache 2.0 license.