-
Notifications
You must be signed in to change notification settings - Fork 2.2k
[Silabs] [Closure] Set initial states for closure endpoints in 917 sample app #39868
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
[Silabs] [Closure] Set initial states for closure endpoints in 917 sample app #39868
Conversation
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.
Code Review
This pull request adds initialization logic for closure control and panel endpoints. A critical bug was identified where the isMoving
state is set incorrectly during initialization. Several readability improvements were suggested by using designated initializers for structs.
PR #39868: Size comparison from 4944739 to 5ec86de Full report (71 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, cyw30739, efr32, esp32, linux, nrfconnect, nxp, psoc6, qpg, stm32, telink, tizen)
|
Summary
This PR adds the logic to set the initial states of the Closure Control and Closure Panel instances during initialization of 917 sample app.
Related issues
N/A
Testing
Built 917 closure app and read the attributes to reflect the state-set during initialization
Readability checklist
The checklist below will help the reviewer finish PR review in time and keep the
code readable:
descriptive
“When in Rome…”
rule (coding style)
See: Pull Request Guidelines