project-chip/connectedhomeip

Support "specification name" across more items within the SDK

Open

#38,891 opened on 2025年5月12日

GitHub で見る
 (1 comment) (0 reactions) (0 assignees)C++ (6,410 stars) (1,659 forks)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
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
3
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
1-2 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
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.