-
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
Remove 'emberAfClusterSecurityCustomCallback' from src/app #3828
Remove 'emberAfClusterSecurityCustomCallback' from src/app #3828
Conversation
bf65e42
to
c23d7d8
Compare
c23d7d8
to
fba1190
Compare
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.
Awesome cleanup!
fba1190
to
3022f96
Compare
I just pushed an update to remove the methods from |
Size increase report for "nrfconnect-example-build" from 7bd7736
Full report output
|
Size increase report for "esp32-example-build" from 7bd7736
Full report output
|
Problem
#3809 list all the callbacks that are kept when migrating to ZAP in #3464. While some definitively makes senses, some others may be some dependencies that does not make sense.
One example of such callback is
emberAfClusterSecurityCustomCallback
since security is not optional in CHIP.This patch has some intersection with #3462 but this is just because
EmberAfProfileId
is used inemberAfClusterSecurityCustomCallback
Summary of Changes
emberAfClusterSecurityCustomCallback
callbacks fromgen/
emberAfClusterSecurityCustomCallback
that was leading to a stub anywaysrc/app/util
. My understanding is that the secure layer is on top of this code, so security features will not be managed by it.