project-chip/connectedhomeip

Support "specification name" across more items within the SDK

Open

#38,891 创建于 2025年5月12日

在 GitHub 查看
 (1 评论) (0 反应) (0 负责人)C++ (6,410 star) (1,659 fork)batch import
good first issuestale

描述

The ZAP templates vary usage of asUpperCamelCase and asUpperCamelCase preserveAcronyms=true and code generation is inconsistent for acronym handling (e.g. C++ and darwin differ).

When preserveAcronyms makes a difference, we should preserve the XML name (with spaces and special characters and all) so that code generation can make a decision on how to encode things.

https://github.com/project-chip/connectedhomeip/pull/38888 adds support for constant names. We should go beyond that:

  • determine a good syntax throughout (for enums/bitmaps/struct/command names, structure member names, cluster names)
  • apply this syntax to update clusters. It is likely constants are the main ones affected though. May need to manually validate (e.g. using the Unit testing cluster)

贡献者指南

技术栈
cpp
领域
toolingbuild system
议题类型
feature
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
fresh
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Understanding of Matter SDK cluster definitionsFamiliarity with ZAP code generation templates
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
35
研究方向
Review the linked PR #38888 to understand the approach for constant names. Determine a consistent syntax for specification names across enums, bitmaps, structs, commands, structure members, and cluster names. Apply the syntax to update clusters, manually validating using the Unit testing cluster. Focus on acronym handling to ensure code generation consistency.