How would you recommend handling situations where multiple modules define on_change behavior for the same field in the same form?
Let's say we have a module dependency structure like this, and each module has their own on_change() method for the same field:
Module A (in core)
--Module B (a community extension)
--Module C (some additional own customization)
When the on_change of Module C gets triggered, what's the best way to make sure that also A and B's on_change methods get called with their correct parameters? Is it possible to somehow define multiple on_change methods for a single field or are you supposed to call the superclass methods similarly as in create(), write() etc. methods?
do the module A onchange and module B onchange methods have the same method name? If so... I don't think it is possible. Otherwise you can call the A and B onchange methods from within the module C onchange method
May be You could Call Super of the onchange Functions in module B and Module A inside the onchange definition of Module C.