Releases: ember-decorators/ember-decorators
Releases · ember-decorators/ember-decorators
v6.1.0
v6.0.0
Breaking Changes
-
Removed Packages
@ember-decorators/babel-transforms@ember-decorators/controller@ember-decorators/data@ember-decorators/service
-
Removed APIs from
@ember-decorators/object@computed@wrapComputed@action- All computed macros
The functionality provided by these APIs is now built into Ember directly! You will be able to use them by importing them from ember, e.g.
import { action, computed } from '@ember/object';You can include these in your app today using the polyfill.
v5.0.0
Breaking Changes
@readOnlyand@volatilehave been removed in favor of@(computed().readOnly())and@(computed().volatile())style declarations. All classic modifiers are available, enabled, and chainable in this way.@readsand@overridableReadshave been removed and changed back to@readOnlyand@readsrespectively, and@oneWayhas been added back.@serviceand@controllerhave both been renamed toinjectto match the exports in Ember proper.- The
shouldThrowOnComputedOverrideconfiguration option has been removed, since it is not an option in Ember proper. - Removed the
macrofunction in favor of compatibility with classic classes
New Features
@computedcan now receive a ComputedPropertyDescriptor as its last argument (e.g. a function or{ get, set }object.- All computed property decorators can now be used in classic classes as well. This makes the decorators a drop-in replacement for
@ember/object#computed. @actionnow binds action methods as well as copying their reference.
v4.0.0
v3.1.0
v3.0.0
Breaking Changes
- The
@readOnlycomputed macro has been renamed to@reads, and the@readsand@oneWaymacros have been renamed to@overridableReads - Computed properties are now overridable (clobberable) by default. You can disable this by setting the
throwOnComputedOverrideoption in the build config.
v2.5.2
v2.5.2