...
| Code Block | ||||
|---|---|---|---|---|
| ||||
<table-element [data]="[{}]" [columnsConfiguration]="columnsConfiguration" (rowClickHandler)="eventListener($click)">
</table-element>
<script>
let columnsConfiguration = [{
title: string,
searchable: boolean,
orderable: boolean,
data: 'key',
visible: boolean,
render: () => {},
paging: boolean,
info: boolean,
autoWidth: boolean,
others: any
}]
</script> |
Filter Component
This generic filter component should work at the chart level, table level, and also at the report Level as global filters.
Moreover, it should handle nested filter capability as well.
selector :- <sb-dashlet-filter>
| Code Block | ||||
|---|---|---|---|---|
| ||||
<sb-dashlet-filter [data]="JSON" [filters]="filters" (filteredData)="subscriptionFunction"> </sb-dashlet-filter>
<script>
let data = [{ key1: any, key2: any }, {key1: any, key2: any}];
filters = [{
header: "string",
footer: "string",
dataExpr: "key1",
filters: [{
header: "string",
footer: "string",
dataExpr: "string",
filters: [{
dataExpr: "key2"
...
}]
}]
}];
</script> |
...
Notes
...
If there are more charts in a single report, then each graph should be lazy-loaded to improve page performance.
client-side caching for the datasets.
...