ngx-feature-toggle
Advanced tools
Changelog
[7.0.0][] - 2023-02-04
NgxSkeletonLoaderModule.forRoot({ theme: /* ...list of CSS atributes */} })
By default when using NgxSkeletonLoaderModule.forRoot({ theme: /* ...list of CSS atributes */} })
the application is using this value as source of truth, overriding any local theming passed to <ngx-feature-toggle>
component via [theme]
input.
By using NgxSkeletonLoaderModule.forRoot({ theme: { extendsFromRoot: true, /* ...list of CSS atributes */} })
in your application, you should also be aware that:
<ngx-feature-toggle>
component will use theme
coming from NgxSkeletonLoaderModule.forRoot()
as the source of truth<!--
// ... E.G: App is using this configuration below
NgxSkeletonLoaderModule.forRoot({
theme: {
// Enabliong theme combination
extendsFromRoot: true,
// ... list of CSS theme attributes
height: '30px',
},
}),
-->
<div class="item">
<ngx-feature-toggle></ngx-feature-toggle>
<!-- above line will produce a skeleton component using `height: 30px;`" -->
<ngx-feature-toggle [theme]="{background: 'blue'}"></ngx-feature-toggle>
<!-- above line will produce a skeleton component using `height: 30px; background: blue;`" -->
<ngx-feature-toggle [theme]="{height: '50px', background: 'red'}"></ngx-feature-toggle>
<!-- above line will produce a skeleton component using `height: 50px; background: red;`" -->
</div>
custom-content
appearance. From now on, consumers can now add their own content inside <ng-skeleton-loader></ng-skeleton-loader>
component. So that, they can add some custom content, such as SVG, as an examplecustom-content
usageChangelog
[6.0.0][] - 2022-08-18
.loader
to .skeleton-loader
The CSS class used as namespace was changed. Previously, it was called .loader
and now is .skeleton-loader
. It might cause some issues in cases of :host
DOM style scoping usage. For the sake of semantic versioning, please bear in mind this scenario in case of :host
usage.