You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a class is created through the Deft.mixin.Controllable mixin, if the class creation fails a generic error is thrown. Would this not be more useful to provide information related to why the class creation failed?
For example if you configure a store but the proxy fails to create, it's difficult to debug the exact point of failure. I'm happy to provide a pul request to fix this issue, I just need to know whether this is a valid request.
Cheers,
Josh
The text was updated successfully, but these errors were encountered:
… Controller classes
Introduced a new Class pre-processor for the `controller` annotation which conditionally calls `Ext.require()` for required classes and applies Controllable behavior whenever it detects the target class is includes the`Deft.mixin.Controllable` mix-in.
Now relying on Ext.Loader() to report some errors that were previously handled internally.
Removed `Deft.mixin.Controllable` test cases that are no longer applicable.
Refactored previous fix for #14 and #15 to align with the new Class pre-processor oriented architecture.
Fixes#17
Hi,
When a class is created through the
Deft.mixin.Controllable
mixin, if the class creation fails a generic error is thrown. Would this not be more useful to provide information related to why the class creation failed?For example if you configure a store but the proxy fails to create, it's difficult to debug the exact point of failure. I'm happy to provide a pul request to fix this issue, I just need to know whether this is a valid request.
Cheers,
Josh
The text was updated successfully, but these errors were encountered: