Releases: lVlyke/lithium-angular
Releases · lVlyke/lithium-angular
7.0.0-beta.0
- Fixed typing issue where component state properties with generic values weren't able to be accessed.
- Fixed typing issue where
DeclareState
decorator wasn't able to reference public named properties with generic values. - Fixed issue where
ComponentStateRef.set
wasn't propagating errors to returned observable chain. - Fixed issues where
ComponentStateRef.sync
was causing infinite loops in some circumstances.
6.1.0
7.0.0-alpha.8
- Fixed issue with
DeclareState
decorator typings wherepublicName
type constraints weren't being enforced. - Fixed issue with
DeclareState
decorator typings where declaring apublicName
resulted in a compiler error for classes containing properties with values of a generic type.
7.0.0-alpha.7
- Fixed regression in typings for
ComponentState
.
7.0.0-alpha.6
@AsyncState
decorator can now take in optional async property source key (defaults to${key}$
).@DeclareState
decorator no longer takes in an options object and only takes an optional Name property key.@AsyncState
and@DeclareState
decorators are now completely type safe.
7.0.0-alpha.5
@DeclareState
decorator now accepts a type safe property key config option to allow for mirroring a private state definition to a public variable.- Added
ComponentStateRef.sync
method for synchronizing two state properties to the same value.
7.0.0-alpha.4
- Component states now use properties declared in base classes with
@DeclareState
and@AsyncState
. ComponentState.create
now supportsforwardRef
.- Added
DirectiveState
type and namespace for creating directive states, which are component states that are injected with a specific injection token to prevent state collisions.
7.0.0-alpha.3
- Added
@DeclareState
property decorator for declaring uninitialized component state. - Resolved issue where component state objects were being incorrectly assigned amongst component instances of the same type.
7.0.0-alpha.2
- Fixed an issue where initial property state values from
@AsyncState
property sources weren't being broadcast to the state subjects. - Component state initialization is now performed on
AfterViewInit
andAfterContentInit
events in addition toOnInit
to ensure late-initialized properties are captured (i.e. from@ViewChild
and@ContentChild
decorators). ComponentStateRef
selector methods now use pending component state if available to ensure state is available inOnInit
and other early events.ComponentStateRef.set
now returns an observable that emits when the state has been set.- Added improved error logging when component state hasn't been properly initialized.
7.0.0-alpha.1
- Fixed issue where component state instances were being initialized multiple times with repeated component instance creation.