There have been many time while creating/editing a custom widget designer's angular controller where I messed something up (missed a dependent module, caused an error while the controller was instantiated, etc...) and Feather cannot instantiate the controller. The default behavior is to just swallow the error and instead instantiate the default controller (DefaultCtrl).
It would be very helpful to at the very least $log a warning of what the error was so that I will more easily know my controller cannot be instantiated and what the issue was.
There have been many time while creating/editing a custom widget designer's angular controller where I messed something up (missed a dependent module, caused an error while the controller was instantiated, etc...) and Feather cannot instantiate the controller. The default behavior is to just swallow the error and instead instantiate the default controller (
DefaultCtrl).It would be very helpful to at the very least $log a warning of what the error was so that I will more easily know my controller cannot be instantiated and what the issue was.