oopman / jquery-plugincreator Goto Github PK

Given plugin A defining the following members:

{
    methodA: function () {
        //TODO: Do stuff
    }
}

Extending plugin A to create plugin B with the following members:

{
    methodA: function(optionalParameter, _super) {
        //TODO: Do stuff and call _super()
    }
}

Attempting to call methodA on an instance of Plugin B with no parameters results in the optionalParameter member receiving the value intended for the _super parameter.

This is a serious issue that breaks non-trivial inheritance usage.

With the decision to implement v2.0.0 of this project it's probably about time to mark the current release of the v0.x line as v1.0.0

v1.0.0 of jQuery PluginCreator will introduce major breaking changes.

The following features/changes are planned:

• Plugins will be written using the ES6 class system. The current DIY OO system will no longer be supported and plugin inheritance will instead performed directly using the plugin one wishes to extend. This will leverage the module system provided by ES6 in order to allow a Plugin module to not only extend jQuery but also make its class available for extension.
• The Plugin functions created by jQuery PluginCreator on the jQuery.fn object will be enhanced in order to use ES5.1 getters and setters in order to ease access to plugin instances.

Given plugin A defining the following members:

{
    methodA: function () {
        //TODO: Do stuff
    }
}

Extending plugin A to create plugin B with the following members:

{
    methodA: function(optionalParameter, _super) {
        //TODO: Do stuff and call _super()
    }
}

Results in plugin A's methodA member being wrapped with the new methodA function intended for plugin B only.