legacy module holds most of the support utilities required to make the old tuple-based configuration syntax work.
LegacyDatatableView as your view’s base class instead of
DatatableView, and then declare a class attribute
datatable_options as usual. This strategy simply translates the old syntax to the new syntax. Certain legacy internal hooks and methods will no longer be available.