-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Rename some cluster_id constants to match cluster name #23471
Conversation
This makes the constant in sync with the cluster name. Spec 6.7 names this 'Content Launcher Cluster' not 'Content Launch'. This will simplify codegen because by knowing cluster name, one can inver cluster constant names.
PR #23471: Size comparison from 5a0e3ce to e67fba6 Increases (13 builds for bl602, bl702, psoc6, qpg, telink)
Decreases (1 build for psoc6)
Full report (35 builds for bl602, bl702, cc13x2_26x2, cyw30739, efr32, k32w, linux, psoc6, qpg, telink)
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is OK as far as it goes, but we should really not have the *_CLUSTER_ID constants at all: SDK consumers should be using the namespaced cluster constants. These things are legacy that we just didn't get around to removing before 1.0....
…23471) * Update constant for CONTENT_LAUNCH to CONTENT_LAUNCER This makes the constant in sync with the cluster name. Spec 6.7 names this 'Content Launcher Cluster' not 'Content Launch'. This will simplify codegen because by knowing cluster name, one can inver cluster constant names. * zap regen * Rename on off switch config to configuration in cluster constants * Restyle * zap regen
…23471) * Update constant for CONTENT_LAUNCH to CONTENT_LAUNCER This makes the constant in sync with the cluster name. Spec 6.7 names this 'Content Launcher Cluster' not 'Content Launch'. This will simplify codegen because by knowing cluster name, one can inver cluster constant names. * zap regen * Rename on off switch config to configuration in cluster constants * Restyle * zap regen
this renames CONTENT_LAUNCH to CONTENT_LAUNCHER and ON_OFF_SWITCH_CONFIG to ON_OFF_SWITCH_CONFIGURATION
This makes the cluster name consistent with the constant - it mostly is, except these few clusters.