AlarmCallbacks with optional configuration fields cannot be loaded #1222
It seems like AlarmCallbacks with configuration fields that are optional cannot be instantiated:
I cannot confirm this at the moment (too far away from a setup where I could reproduce this) but it might be related to the changes made in 8966e3f and configuration keys that have values that are now null and before that just were not set at all.
This will most likely break any alarm callback plugin that has optional fields which are not set by the user.
@florianvolle We should think about how to integrate the plugin interfaces into our QA process. I think they are pretty left out at the moment.
The text was updated successfully, but these errors were encountered: