WML Angular Components Base extends the WML Components Base by integrating it with Angular-specific features and functionality. It builds on the foundation provided by the core library and adds seamless integration with Angular’s framework, making it easier to work with Angular modules, change detection, and Angular-based services like ngx-translate.
While WML Components Base provides the essential UI building blocks, WML Angular Components Base enhances these components to work natively with Angular. This includes adding support for Angular’s dependency injection, change detection, routing, and lifecycle hooks.
Terminal window
npm install -s --verbose @windmillcode/angular-wml-components-base
if you want a different animation for you animation states simply use a different keyframe mabye suffixing the keyframes with open and close for organization<iframe src="https://stackblitz.com/edit/stackblitz-starters-7bnu7v?ctl=1&embed=1&file=src%2Fmain.ts&theme=dark" style="width: 100%; height: calc(500/16 * 1em) !important;"></iframe>
Custom Components
nearly as same as WMLCustomComponent. Refer toWMLCustomComponent
ExtendsWMLMotionUIProperty
Property | Type | Description |
---|---|---|
motionEndEvent |
Subject<WMLMotionUIPropertyState> |
Subject triggered when a motion ends. |
motionKeyFrameEvent |
Subject<string> |
Subject triggered at specific keyframes during css transitions. |
Property | Type | Description |
---|---|---|
ngxTranslateLoaderFactory |
Function |
A function that returns a new instance of WMLNGXTranslateLoader . |
Property | Type | Description |
---|---|---|
i18nLocation |
(lang: string) => any |
A function that returns the translation file or object based on the language code. |
Method | Description |
---|---|
getTranslation(lang: string) |
Fetches the translations for the given language and returns an observable with the translation data. |
Parameter | Type | Description |
---|---|---|
vcf |
ViewContainerRef |
Angular ViewContainerRef for creating the component. |
cpnt |
Type<any> |
Component type to be created. |
props |
any |
Properties to be passed to the component. |
return |
ComponentRef<any> |
Returns a reference to the created component. |
, |
pulled features from seperated angular features from core library to angular-wml-components-base creating WMLAngularTestUtils,WMLAngularTestHttpHandler,WMLAngularModuleForRootProps,WMLAngularMotionUIProperty WMLAngularCustomComponent from their orginal respective part which exlude “Angular in their name”
updated package to reflect the version 18.2.3 of @angular/core package
updated package to reflect the version 18.2.3 of @angular/core package
updated package to reflect the version 18.2.3 of @angular/core package
updated package to conform with @windmillcode/angular-wml-components-base
updated package to conform with @windmillcode/angular-wml-components-base
updated package to conform with @windmillcode/angular-wml-components-base
[UPDATE] added motionKeyFrameEvent for css transitions WMLAngularMotionUIPropertyupdated package to conform with @windmillcode/wml-components-base
updated package to reflect the version 18.2.4 of @angular/core package
updated package to reflect the version 18.2.4 of @angular/core package
updated package to conform with @windmillcode/wml-components-base
updated package to conform with @windmillcode/wml-components-base
updated package to reflect the version 18.2.5 of @angular/core package
updated package to reflect the version 18.2.6 of @angular/core package
updated package to reflect the version 18.2.7 of @angular/core package
updated package to conform with @windmillcode/wml-components-base
updated package to conform with @windmillcode/wml-components-base
updated package to conform with @windmillcode/wml-components-base
[PATCH] WMLAngularMotionUIProperty
constructor got updated in projects/wml-angular-components-base/src/lib/models.ts
to take partial props, fixing a bug where custom props were not being overridden just know that for the time being you can only use WMLMotionUIProperty or WMLAngularMotionUIProperty you cant use both becuase internally there would be a conflict with the management of static variables between the two classes
updated package to reflect the version 18.2.8 of @angular/core package
updated package to reflect the version 18.2.8 of @angular/core package
updated package to reflect the version 18.2.8 of @angular/core package
updated package to conform with @windmillcode/wml-components-base
updated package to conform with @windmillcode/wml-components-base
updated package to conform with @windmillcode/wml-components-base
updated package to conform with @windmillcode/wml-components-base
updated package to conform with @windmillcode/wml-components-base
updated package to conform with @windmillcode/wml-components-base
updated package to conform with @windmillcode/wml-components-base