Adds methods (from issue title) to DT proto as relays to the ModelList methods. Is this worth splitting out to an extension instead of just putting it in Core?
Having this be a class extension suggests the core implementation should not include state change subscriptions for data (or by association, columns), requiring the implementer to update the ML and manually call table.body.render() again to replace the <tbody> wholesale. This extension then replaces the manual work that would have been done, and should do the right thing by preserving existing DOM elements (or should it prefer performance?)
Auto-mix()ed class extension.
Adds methods (from issue title) to DT proto as relays to the ModelList methods. Is this worth splitting out to an extension instead of just putting it in Core?
Having this be a class extension suggests the core implementation should not include state change subscriptions for
data(or by association,columns), requiring the implementer to update the ML and manually calltable.body.render()again to replace the<tbody>wholesale. This extension then replaces the manual work that would have been done, and should do the right thing by preserving existing DOM elements (or should it prefer performance?)