-
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
Make zap_cluster_list.py a little more flexible. #25089
Make zap_cluster_list.py a little more flexible. #25089
Conversation
Instead of hardcoding the data, have it load it from a json file.
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.
👍
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.
What is the difference - it is still hard-coding, but now instead of one file there are 2 files (or if we just consider the file that has to be modified for things, then it is still 1 file to modify).
It does separate the data from processing, so it would potentially help if we intend to add more different logic for what clusters are included in our sdk. If we go that route, maybe we should add this to the PR description.
PR #25089: Size comparison from d2e4c4a to 7f51bba Increases (3 builds for esp32, telink)
Decreases (17 builds for bl602, bl702, cyw30739, esp32, nrfconnect, psoc6, qpg, telink)
Full report (40 builds for bl602, bl702, cc13x2_26x2, cc32xx, cyw30739, efr32, esp32, linux, mbed, nrfconnect, psoc6, qpg, telink)
|
Instead of hardcoding the data, have it load it from a json file.
Instead of hardcoding the data, have it load it from a json file.
There are two benefits to this: