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.