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
[ ] bug report => Search github for a similar issue or PR before submitting
[ X] feature request => Please check if request is not on the roadmap already https://github.com/primefaces/primeng/wiki/Roadmap
[ ] support request => Please do not submit support request here, instead see http://forum.primefaces.org/viewforum.php?f=35
Expected behavior
Whenever the datatable has changed its value and dataToRender and totalRecords, an event should be called. similar to (filter) and (sort) it sould be a (value) or (changed) or (valueChanged) or (init) or (updated) event.
What is the motivation / use case for changing the behavior?
I need to know when the dataTable has updated so I can print out the result count which you typically see on google searches.
Please tell us about your environment:
Visual Studio Code on Windows 10
Angular version: 4.3.3
PrimeNG version: 4.1.2
Browser: [all]
Language: [all]
Node (for AoT issues):node --version = v6.11.0
The text was updated successfully, but these errors were encountered:
orsolli
pushed a commit
to orsolli/primeng
that referenced
this issue
Aug 7, 2017
Expected behavior
Whenever the datatable has changed its value and dataToRender and totalRecords, an event should be called. similar to (filter) and (sort) it sould be a (value) or (changed) or (valueChanged) or (init) or (updated) event.
Minimal reproduction of the problem with instructions
Plunker demomstrating the missing feature:
http://plnkr.co/edit/CDlCwguEEkiT95LjjAcZ?p=preview
What is the motivation / use case for changing the behavior?
I need to know when the dataTable has updated so I can print out the result count which you typically see on google searches.
Please tell us about your environment:
Visual Studio Code on Windows 10
Angular version: 4.3.3
PrimeNG version: 4.1.2
Browser: [all]
Language: [all]
Node (for AoT issues):
node --version
= v6.11.0The text was updated successfully, but these errors were encountered: