Skip to content
代码片段 群组 项目
  • Bharat Dandu's avatar
    f738a4fd
    Switching to use templateUtil.ensureZclPackageIds instead of... · f738a4fd
    Bharat Dandu 创作于
    Switching to use templateUtil.ensureZclPackageIds instead of templateUtil.ensureZclPackageId to handle the custom xml generation which is not being accounted for currently when loading custom xml from the UI
    
    Updating helper-endpointconfig, types and zcl-util to use packageIds instead of packageId to handle custom xml
    
    - Updating one of the helper tests to have packageIds as well just like the packageId
    
    Switching to packageIds in a session to resolve the custom xml addition use case
    
    - Switching to packageIds in query-data-type-discriminator.js, zcl-loader.js to make sure we have the data type discriminators defined from standard xml for the custom xml
    - Adding known packages to queries related to query-loader, zcl-loader-silabs to handle custom xml additions
    
    Switching to packageIds and formatting the sql queries
    
    Switching to packageIds for enums, bitmaps and structs such that custom xml additions are accounted for and removing cache for query-atomic because past testing in the local machine showed not using cache was faster.
    
    Adding tests for custom xml generation
    
    Updating api doc
    
    Cleaning up function descriptions and fixing the test failures related to automaticallyCreateFields being called for undefined
    Github: ZAPP#622
    
    Switching to use ensureZclPackageIds instead of ensureZclPackageId for handling custom xml correctly in matter
    
    Cleaning up docs and typos
    
    Using dbApi.toInClause for the SQL IN clauses such that the queries don't break when we internationalize to different languages
    
    Gihub: ZAP#622
    f738a4fd
    历史
    Switching to use templateUtil.ensureZclPackageIds instead of...
    Bharat Dandu 创作于
    Switching to use templateUtil.ensureZclPackageIds instead of templateUtil.ensureZclPackageId to handle the custom xml generation which is not being accounted for currently when loading custom xml from the UI
    
    Updating helper-endpointconfig, types and zcl-util to use packageIds instead of packageId to handle custom xml
    
    - Updating one of the helper tests to have packageIds as well just like the packageId
    
    Switching to packageIds in a session to resolve the custom xml addition use case
    
    - Switching to packageIds in query-data-type-discriminator.js, zcl-loader.js to make sure we have the data type discriminators defined from standard xml for the custom xml
    - Adding known packages to queries related to query-loader, zcl-loader-silabs to handle custom xml additions
    
    Switching to packageIds and formatting the sql queries
    
    Switching to packageIds for enums, bitmaps and structs such that custom xml additions are accounted for and removing cache for query-atomic because past testing in the local machine showed not using cache was faster.
    
    Adding tests for custom xml generation
    
    Updating api doc
    
    Cleaning up function descriptions and fixing the test failures related to automaticallyCreateFields being called for undefined
    Github: ZAPP#622
    
    Switching to use ensureZclPackageIds instead of ensureZclPackageId for handling custom xml correctly in matter
    
    Cleaning up docs and typos
    
    Using dbApi.toInClause for the SQL IN clauses such that the queries don't break when we internationalize to different languages
    
    Gihub: ZAP#622
代码所有者
将用户和群组指定为特定文件更改的核准人。 了解更多。