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
@austinrivas I'm using the fnInitComplete callback to do some DOM manipulation (basically to add some custom buttons to the table header along with the filter and length). However, it appears this is not playing nicely with the reactive query because every time it changes, the callback is re-run.
I just thought this was a little weird because using other elements such as the table length, the pagination or the filter don't cause the callback to be re-run.
I know the DOM manipulation is a bit of a hack anyway, so it's not a huge deal, but I just thought I'd flag it.
The text was updated successfully, but these errors were encountered:
I am currently destroying and rerendering the table whenever the query changes by using the DataTables destroy option. However it seems like redrawing the table using the drawCallback is a better approach.
I'll try to implement this using your example asap.
I have a similar problem. I use initComplete for row clicking and get _id of current clicked row. If I update a displayed property externally, the column displays the correct text reactively but after that the row clicking event doesn't work at all.
@austinrivas I'm using the fnInitComplete callback to do some DOM manipulation (basically to add some custom buttons to the table header along with the filter and length). However, it appears this is not playing nicely with the reactive query because every time it changes, the callback is re-run.
I just thought this was a little weird because using other elements such as the table length, the pagination or the filter don't cause the callback to be re-run.
I know the DOM manipulation is a bit of a hack anyway, so it's not a huge deal, but I just thought I'd flag it.
The text was updated successfully, but these errors were encountered: