- No changes.
- No changes.
- No changes.
-
Y.Base.create()can now be used withY.BaseCore, in addition to its existing usage withY.Base. This allows non-observable, BaseCore hierarchies to use class extensions. -
Extracted the
Y.BaseObservableclass extension fromY.Base. This is a new class extension forY.BaseCorewhich adds support for observability. This allows BaseCore subclasses to mix-in BaseObservable at runtime, bringing their functionality up to that ofY.Base.
- No changes.
- No changes.
- No changes.
- No changes.
-
"value" defined in a subclass ATTRS definition, will now override "valueFn" for the same attribute from the superclass chain.
Previously, "value" would only override "value" and "valueFn" would only overide "valueFn", and in the aggregated set of attributes, "valueFn" would take precedence over "value".
This meant that subclasses had to define a "valueFn" to overide superclasses, if the superclass used "valueFn".
- No changes.
-
Only invoke Base constructor logic once to support multi-inheritance scenario in which an extension passed to Base.create inherits from Base itself.
NOTE: To support multiple inhertiance more deeply, we'd need to remove the hasOwnProperty restriction around object key iteration.
-
Added Y.BaseCore which is core Base functionality without Custom Events (it uses Y.AttributeCore instead of Y.Attribute).
Y.BaseCore still maintains the ATTRS handling, init/destroy lifecycle and plugin support, but doesn't fire any custom evnets of it's own (the idea is that it will the base for Node-Plugin type components, built off of a WidgetCore)
Y.Base is now Y.BaseCore + Y.Attribute, and is 100% backwards compatible.
Summary:
Y.Attribute - Common Attribute Functionality (100% backwards compat) Y.Base - Common Base Functionality (100% backwards compat)
Y.AttributeCore - Lightest Attribute support, without CustomEvents Y.BaseCore - Lightest Base support, without CustomEvents
--
Y.AttributeEvents - Augmentable Attribute Events support Y.AttributeExtras - Augmentable 20% usage for Attribute (modifyAttr, removeAttr, reset ...) Y.AttributeComplex - Augmentable support for constructor complex attribute parsing ({"x.y":foo})
--
Y.Attribute = Y.AttributeCore + Y.AttributeEvents + Y.AttributeExtras Y.Base = Y.BaseCore + Y.Attribute
--
Modules:
"base-base" : Y.Base "base-core" : Y.BaseCore
"base-build" : Y.Base.build/create/mix mixin
-
Extended Base.create/mix support for _buildCfg, to Extensions, mainly so that extensions can define a whitelist of statics which need to be copied to the main class.
e.g.
MyExtension._buildCfg = { aggregates:["newPropsToAggregate"...], custom: { newPropsToCustomMix }, statics: ["newPropsToCopy"] };
- No changes.
-
Base now destroys plugins before destroying itself
-
Base.create/mix extensions can now define initializer and destructor prototype functions, which will get invoked after the initializer for the host class into which they are mixed and before it's destructor.
-
Use a hash version of whitelist mix for improved performance. Also removed non-required hasOwnProperty check and delete.
-
Fixed Base.mix when used on a class created using Base.create
-
toString no longer inadvertently stamps the object, however, we now stamp Base objects in the constructor, to support use cases where the "toString" stamping was implicitly being relied upon (e.g. in DD, as hashkeys).
- Fixed Base.create to properly isolate ATTRS on extensions
- No changes
-
As the final step in the destroy phase, Base now does a detachAll() to avoid invoking listeners which may be waiting to be in an async. step which occurs after destruction.
-
"init" and "destroy" events are now published with the defaultTargetOnly property set to true
-
Added support for MyClass.EVENT_PREFIX to allow developers to define their own event prefix
-
Made "init" and "destroy" events fireOnce:true (along with "render" in Widget), so that subscriptions made after the events are fired, are notified immediately.
-
Dynamic and non-dynamically built classes now have their extensions instantiated the same way - during _initHierarchy.
-
Updated ATTRS handling for Base.build, so that ATTRS are also aggregated at the attribute configuration object level, allowing extensions to add to, or overwrite, attribute configuration properties on the host.
-
Added sugar Base.create and Base.mix methods on top of Base.build, to simplify the 2 main use cases:
- Creating a completely new class which uses extensions.
- Mixing in extensions to an existing class.
-
Documented non-attribute on, after, bubbleTargets and plugins property support in the Base constructor config argument
-
Fixed hasImpl method on built classes, to look up the class hierarchy for applied extensions.
-
Plugin.Host removed from base-base module and delivered as it's own module - "pluginhost"
-
base broken up into..
base-base: Provides class hierarchy support for ATTRS and initialization
base-build: Provides Extension support in the form of Base.build
base-pluginhost: Augments Plugin.Host to Base, adding plugin support
-
Config argument for init event now merged into the event facade, instead of being passed separately (available as e.cfg).
-
Removed Base.create. On review, considered to be overkill. Users can easily create new instances, using Base.build
-
Moved PluginHost down from Widget to Base, since utils and Node will also support Plugins.
-
PluginHost.plug and unplug now accept the plugin class as arguments [plug(pluginClass, cfg) and unplug(pluginClass)].
-
Split base module up into base-base and base-build.
-
Added lazy attribute initialization support, to improve performance.
This also removes order dependency when processing ATTRS for a particular class.
If a get/set call is made for an uninitialized attribute A, in the getter/setter/validator or valueFns of another attribute B, A will be intiailized on the fly.
-
Added ability to subscribe to on/after events through the constructor config object, e.g.:
new MyBaseObject({ on: { init: handlerFn, myAttrChange: handlerFn }, after: { init: handlerFn, myAttrChange: handlerFn }, ... });
-
Developers can now override the default clone behavior we use to isolate default ATTRS config values, using cloneDefaultValue, e.g.:
ATTRS = { myAttr : { value: AnObjectOrArrayReference cloneDefaultValue: true|false|"deep"|"shallow" } }
If the cloneDefaultValue property is not defined, Base will clone any Arrays or Object literals which are used as default values when configuring attributes for an instance, so that updates to instance values do not modify the default value.
This behavior can be over-ridden using the cloneDefaultValue property:
true, deep:
Use Y.clone to protect the default value.
shallow:
Use Y.merge, to protect the default value.
false:
Don't clone Arrays or Object literals. The value is intended to be used by reference, for example, when it points to a utility object.
-
Base.plug and Base.unplug used to add static Plugins (default plugins for a class). Replaces static PLUGINS array, allowing subclasses to easily unplug static plugins added higher up in the hierarchy.
-
Base adds all attributes lazily. This means attributes don't get initialized until the first call to get/set, speeding up construction of Base based objects.
Attributes which have setters which set some other state in the object, can configure the attribute to disable lazy initialization, by setting lazyAdd:false as part of their attribute configuration, so that the setter gets invoked during construction.