You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As of now ng-table directive can be used as a attribute on a table element. This reduce the ability to manage the table behaviour based on ngTable scope.
As an alternative can we extend it to be used as element directive / or div attribute direcevtive and child table element
it will looks like this.
<div ng-table="vm.tableParam">
<div>
</div>
<table>
<-- here goes the real table defenition -->
</table>
</div>
This enabled the user to have better control of ng-table scope out of the table element, and can display custom warning messages out of the real table without affecting the real table and not much complexity to use ng-table events.
This helps user to show a progressbar on top of the table when a reload happens
This helps to show additional information about the table
This even can specify footer and header rows so that pagination related information can be easily handled
Let me know your opinion, since there are no updates happened on it from long time and not compatible with latest angular, don't know how many its useful.
The text was updated successfully, but these errors were encountered:
As of now ng-table directive can be used as a attribute on a table element. This reduce the ability to manage the table behaviour based on ngTable scope.
As an alternative can we extend it to be used as element directive / or div attribute direcevtive and child table element
it will looks like this.
This enabled the user to have better control of ng-table scope out of the table element, and can display custom warning messages out of the real table without affecting the real table and not much complexity to use ng-table events.
Let me know your opinion, since there are no updates happened on it from long time and not compatible with latest angular, don't know how many its useful.
The text was updated successfully, but these errors were encountered: