For most action callbacks the data reported in the state parameter should also be accessible though the device itself, e.g. on(). Instead of having all of this duplicate data we should just access it though the device.
One exception might be the battery state as that is not something we (currently) store and probably won't store either.
One potential issue though would maybe be the data changing during the callback? Not sure if that would really lead to issues though.
For most action callbacks the data reported in the state parameter should also be accessible though the device itself, e.g. on(). Instead of having all of this duplicate data we should just access it though the device.
One exception might be the battery state as that is not something we (currently) store and probably won't store either.
One potential issue though would maybe be the data changing during the callback? Not sure if that would really lead to issues though.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
For most action callbacks the data reported in the state parameter should also be accessible though the device itself, e.g. on(). Instead of having all of this duplicate data we should just access it though the device.
One exception might be the battery state as that is not something we (currently) store and probably won't store either.
One potential issue though would maybe be the data changing during the callback? Not sure if that would really lead to issues though.