Skip to content

Rename closure-dimension cluster files for conversion to code driven#43573

Open
pimpalemahesh wants to merge 3 commits intoproject-chip:masterfrom
pimpalemahesh:closure-dimension/rename-files
Open

Rename closure-dimension cluster files for conversion to code driven#43573
pimpalemahesh wants to merge 3 commits intoproject-chip:masterfrom
pimpalemahesh:closure-dimension/rename-files

Conversation

@pimpalemahesh
Copy link
Contributor

@pimpalemahesh pimpalemahesh commented Mar 13, 2026

Changes

This MR renames the Closure Dimension cluster source files to follow the code driven cluster style.

Only file renames

  • closure-dimension-server.cpp → ClosureDimensionCluster.cpp
  • closure-dimension-server.h → ClosureDimensionCluster.h
  • closure-dimension-delegate.h → ClosureDimensionClusterDelegate.h
  • closure-dimension-cluster-logic.cpp → ClosureDimensionClusterLogic.cpp
  • closure-dimension-cluster-logic.h → ClosureDimensionClusterLogic.h
  • closure-dimension-matter-context.cpp → ClosureDimensionClusterMatterContext.cpp
  • closure-dimension-matter-context.h → ClosureDimensionClusterMatterContext.h
  • closure-dimension-cluster-objects.h → ClosureDimensionClusterObjects.h

Related issues

#43574

Testing

Successfully built closure-app locally.
CI should be enough as only file renames

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request refactors the Closure Dimension cluster files to align with the code-driven cluster style. The changes primarily involve renaming files, moving code into new files, and updating the old headers to act as wrappers for backward compatibility. The build file modifications are consistent with these changes. The refactoring is well-executed, and the identified minor copy-paste error in a file-level comment should be corrected for clarity.

@github-actions
Copy link

PR #43573: Size comparison from fa956ce to 0dc7778

Full report (5 builds for cc32xx, realtek, stm32)
platform target config section fa956ce 0dc7778 change % change
cc32xx air-purifier CC3235SF_LAUNCHXL FLASH 558106 558106 0 0.0
RAM 204504 204504 0 0.0
lock CC3235SF_LAUNCHXL FLASH 591230 591230 0 0.0
RAM 204744 204744 0 0.0
realtek light-switch-app rtl8777g FLASH 720520 720520 0 0.0
RAM 113448 113448 0 0.0
lighting-app rtl8777g FLASH 767736 767736 0 0.0
RAM 114688 114688 0 0.0
stm32 light STM32WB5MM-DK FLASH 478820 478820 0 0.0
RAM 141324 141324 0 0.0

@pimpalemahesh pimpalemahesh force-pushed the closure-dimension/rename-files branch from 0dc7778 to c44c2fc Compare March 13, 2026 12:09
@pimpalemahesh pimpalemahesh marked this pull request as ready for review March 13, 2026 12:18
@github-actions
Copy link

github-actions bot commented Mar 13, 2026

PR #43573: Size comparison from fa956ce to c44c2fc

Full report (34 builds for bl602, bl616, bl702, bl702l, cc13x4_26x4, cc32xx, efr32, esp32, nrfconnect, nxp, psoc6, qpg, realtek, stm32, telink)
platform target config section fa956ce c44c2fc change % change
bl602 lighting-app bl602+mfd+littlefs+rpc FLASH 1089396 1089396 0 0.0
RAM 144762 144762 0 0.0
bl616 lighting-app bl616+thread FLASH 1100324 1100324 0 0.0
RAM 104184 104184 0 0.0
bl616+wifi+shell FLASH 1586916 1586916 0 0.0
RAM 98080 98080 0 0.0
bl702 lighting-app bl702+eth FLASH 1052752 1052752 0 0.0
RAM 108357 108357 0 0.0
bl702l contact-sensor-app bl702l+mfd+littlefs FLASH 890764 890764 0 0.0
RAM 105748 105748 0 0.0
cc13x4_26x4 lighting-app LP_EM_CC1354P10_6 FLASH 779164 779164 0 0.0
RAM 103324 103324 0 0.0
lock-ftd LP_EM_CC1354P10_6 FLASH 786528 786528 0 0.0
RAM 108508 108508 0 0.0
pump-app LP_EM_CC1354P10_6 FLASH 732724 732724 0 0.0
RAM 97316 97316 0 0.0
pump-controller-app LP_EM_CC1354P10_6 FLASH 716160 716160 0 0.0
RAM 97476 97476 0 0.0
cc32xx air-purifier CC3235SF_LAUNCHXL FLASH 558106 558106 0 0.0
RAM 204504 204504 0 0.0
lock CC3235SF_LAUNCHXL FLASH 591230 591230 0 0.0
RAM 204744 204744 0 0.0
efr32 lock-app BRD4187C FLASH 971196 971196 0 0.0
RAM 125796 125796 0 0.0
BRD4338a FLASH 769268 769260 -8 -0.0
RAM 236544 236544 0 0.0
window-app BRD4187C FLASH 1074656 1074656 0 0.0
RAM 126440 126440 0 0.0
esp32 all-clusters-app c3devkit DRAM 98356 98356 0 0.0
FLASH 1596564 1596564 0 0.0
IRAM 93514 93514 0 0.0
nrfconnect all-clusters-app nrf52840dk_nrf52840 FLASH 857588 857588 0 0.0
RAM 161999 161999 0 0.0
nxp contact mcxw71+release FLASH 735808 735808 0 0.0
RAM 66936 66936 0 0.0
psoc6 all-clusters cy8ckit_062s2_43012 FLASH 1708508 1708508 0 0.0
RAM 213940 213940 0 0.0
all-clusters-minimal cy8ckit_062s2_43012 FLASH 1607180 1607180 0 0.0
RAM 210812 210812 0 0.0
light cy8ckit_062s2_43012 FLASH 1470412 1470412 0 0.0
RAM 196988 196988 0 0.0
lock cy8ckit_062s2_43012 FLASH 1497092 1497092 0 0.0
RAM 224732 224732 0 0.0
qpg lighting-app qpg6200+debug FLASH 840636 840636 0 0.0
RAM 127780 127780 0 0.0
lock-app qpg6200+debug FLASH 779312 779312 0 0.0
RAM 118728 118728 0 0.0
realtek light-switch-app rtl8777g FLASH 720520 720520 0 0.0
RAM 113448 113448 0 0.0
lighting-app rtl8777g FLASH 767736 767736 0 0.0
RAM 114688 114688 0 0.0
stm32 light STM32WB5MM-DK FLASH 478820 478820 0 0.0
RAM 141324 141324 0 0.0
telink bridge-app tl7218x FLASH 728648 728648 0 0.0
RAM 95760 95760 0 0.0
light-app-ota-compress-lzma-shell-factory-data tl3218x FLASH 852792 852792 0 0.0
RAM 44176 44176 0 0.0
tl7218x FLASH 844196 844196 0 0.0
RAM 99564 99564 0 0.0
light-switch-app-ota-compress-lzma-factory-data tl7218x_retention FLASH 725462 725462 0 0.0
RAM 55740 55740 0 0.0
light-switch-app-ota-compress-lzma-shell-factory-data tlsr9528a FLASH 788030 788030 0 0.0
RAM 74916 74916 0 0.0
light-switch-app-ota-factory-data tl3218x_retention FLASH 725458 725458 0 0.0
RAM 33220 33220 0 0.0
lighting-app-ota-factory-data tlsr9118bdk40d FLASH 616200 616200 0 0.0
RAM 118232 118232 0 0.0
lighting-app-ota-rpc-factory-data-4mb tlsr9518adk80d FLASH 842966 842970 4 0.0
RAM 97272 97272 0 0.0

Copy link
Contributor

@andy31415 andy31415 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ok in general. I wonder if the header should go to Cluster or CodegenIntegration (historically leaning towards CodegenIntegration)

@codecov
Copy link

codecov bot commented Mar 13, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 54.07%. Comparing base (fa956ce) to head (c44c2fc).

Additional details and impacted files
@@           Coverage Diff           @@
##           master   #43573   +/-   ##
=======================================
  Coverage   54.07%   54.07%           
=======================================
  Files        1548     1548           
  Lines      106709   106709           
  Branches    13308    13308           
=======================================
  Hits        57704    57704           
  Misses      49005    49005           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@andy31415
Copy link
Contributor

Ok in general. I wonder if the header should go to Cluster or CodegenIntegration (historically leaning towards CodegenIntegration)

@pimpalemahesh we have updated docs on renames: https://project-chip.github.io/connectedhomeip-doc/guides/migrating_ember_cluster_to_code_driven.html#part-0-optimizing-for-an-easier-review

Provides more details on what to rename to what else.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants