Releases: lVlyke/lithium-angular
Releases · lVlyke/lithium-angular
8.0.0
7.3.1
7.3.0
7.2.2
7.2.1
7.2.0
7.1.0
7.0.0
The 7.0.0 release introduces a new concept called component states, which are a type-safe and lightweight alternative to the @StateEmitter
decorator for enabling reactive state management in components. 7.0.0 is fully backwards compatible with prior versions of Lithium, however certain features have been marked as deprecated and will be removed in future versions of Lithium.
Please see the new migration guide for a full guide on how to migrate from prior versions of Lithium to the new component state syntax.
- Added
ComponentState
type for capturing a component's state through a reactive interface. - Added
ComponentStateRef
class, which is an injected service provided at the component level for retrieving itsComponentState
. - Added
createComponentState
function (aliased byComponentState.create
) for creating aComponentStateRef
provider for a given component. - Added
DirectiveState
type for capturing a directive's state through a reactive interface. - Added
DirectiveStateRef
class, which is an injected service provided at the directive level for retrieving itsDirectiveState
. - Added
createDirectiveState
function for creating aDirectiveStateRef
provider for a given directive. - Added
stateTokenFor
function for retrieving the injection token of a provider created withcreateDirectiveState
orcreateComponentState
. - Added
@AsyncState
property decorator for creating synchronous aliases of observable properties inside a component. - Added
@DeclareState
property decorator for declaring uninitialized component state. - Component states fully support
AutoPush
functionality. - Deprecated
LiComponent
base class. - Removed previously deprecated
AotAware
base class. - Removed previously deprecated
AutoPush
class decorator.
Take a look at the newly rewritten intro guide and the example project to see examples of component state usage.
7.0.0-rc.5
- Fixed issue where using
ComponentState
together withStateEmitter
caused proxy values fromStateEmitter
to not behave correctly. - Fixed issue where
StateEmitter
proxy values weren't behaving correctly when written to before being read.
7.0.0-rc.4
- Removed
DirectiveState.CreateOptions.uniqueToken
config option.