For a high level overview of DataTables 3, please see the following documentation:
Since the 3.0.0-beta.2 release there have been a number of changes and few new features, which are detailed below.
For a full description of the changes in this major release since the last non-beta release, please refer to the release notes for the two betas:
DataTable.key() which is used to register a license key for use with DataTables Plus extensions (e.g. Editor and CardView).pageLength), a temporary option for that value will be added so it is less confusing for the end user.DataTable.Dom.s(document).on('ready'...) event. This is provided as a convenience rather than needing to listen for DOMContentLoaded and take account of if the document has already loaded or not.data-dt-row and data-dt-column selectors weren't working correctlycolumns().widths() didn't correctly take into account Responsive hidden columnsdata is provided as a string for DataTable.ajax it wasn't submittingautocomplete=off attributes to table input controls to improve accessabilityon are now automatically removed if a table is destroyeddom, pagingType and orderCellsTop where marked for removal in v3, but they are too widely used to remove at the moment. Only dom takes much code (and even then, not much) but it would be the most disruptive. Removing them from v3 deprecation target.There have been no functional changes in the software since its beta release. For a full description of the changes in this major release since the last non-beta release, please refer to the beta's release notes:
There is just one fix in this release compared to the previous beta of this software (see details below).
For a full description of the changes in this major release since the last non-beta release, please refer to the beta's release notes:
There have been no functional changes in the software since the beta release. For a full description of the changes in this major release since the last non-beta release, please refer to the beta's release notes:
There is just one fix in this release compared to the previous beta of this software (see details below).
For a full description of the changes in this major release since the last non-beta release, please refer to the beta's release notes:
There have been no functional changes in the software since the beta release. For a full description of the changes in this major release since the last non-beta release, please refer to the beta's release notes:
There has been just a single new addition since the previous beta, which is to have the display view automatically update if the host row's data is invalidated in the main table.
For a full description of the changes in this major release since the last non-beta release, please refer to the beta's release notes:
There have been no functional changes in the software since the beta release. For a full description of the changes in this major release since the last non-beta release, please refer to the beta's release notes:
There have been no functional changes in the software since the beta release. For a full description of the changes in this major release since the last non-beta release, please refer to the beta's release notes:
There have been no functional changes in the software since the beta release. For a full description of the changes in this major release since the last non-beta release, please refer to the beta's release notes:
Moveover, Editor is now available on the DataTables CDN and the public NPM repository!
Editor is now part of the DataTables Plus suite of extensions and requires a license key to use. If you have an existing Editor license, your license key is available on your DataTables account page.
Further details on updating to Editor 3 are available in this upgrades notes document, which also highlights the major new features.
The release notes below document the specific changes.
static display controller which can be used to display the Editor form in a pre-defined element. This is primarily designed for use with a form that is always visible (i.e. standalone page editing).dataSrc option which can be used to tell Editor where to get the data to edit from. Specifically in addition to the HTML and DataTable sources that it could proviously do, this option can now be explicity set to ajax to have the form read remote data without needing a source DataTable.ajax.replacements will now apply to the Ajax calls made by upload and uploadMany.on option which can be used to assign event handlers during initialisation. This matches DataTables' own on option.template can now be given a template as the element to use as the template. In this case the contents are cloned and used as the form template. If any other element type is used, the original method of detaching the element and using it directly is still used.attr parameter for fields to set the validation conditions and the new fields.errorText option to set the error message. The error state is only triggered when the form is submitted. Server-side validation is uneffected.ajax option for autocomplete and tags can now be given as an object to provide fine-grained control over the Ajax request.display can now be given as a CSS selector string, which will result in static being used with the given selector used to pick the element that the form will be displayed in. This is just an easy shorthand for static.fields() undeprecated. It is tiny and can still be useful. No intention to remove it, so will keep it in place.ajax.replacements can now have a value set to false, and as a special case, id if specified will cause the default _id_ / {id} replacement not to happen (i.e. you can now specify your own replacement, or cancel the default action).close event to be triggered after an instance was destroyed. No longer._id_ if id has a value.uploadMany is disabled, upload and remove buttons should be removedstatic display controller exampleDataTable class to enable reading of data from a database table without needing to use the Editor class (which is the read / write equivalent).Editor.Fields() and DataTable.Columns() methods for adding multiple columns with an array (IEnumerable more specifically)Editor.Field() with an array is now deprecatedMicrosoft.Data.SqlClient, updated from System.Data.SqlClient.DataTable class to enable reading of data from a database table without needing to use the Editor class (which is the read / write equivalent).exports option in package.json.DataTable class to enable reading of data from a database table without needing to use the Editor class (which is the read / write equivalent).New Python port of the libraries for DataTables, providing full support for Editor.
]]>There is just one change since the v2 beta release, which is noted below.
For a full description of the changes in this major release since the last non-beta release, please refer to the beta's release notes:
There have been a couple of new features and bug fixes made in this release, since the previous beta, including a new info content type. Please refer to the specifics below.
For a full description of the changes in this major release since the last non-beta release, please refer to the beta's release notes:
info content type which will show a tooltip providing extra information about a column without clutter the screen.DataTable.render.date() was used without moment or luxon on the page, date picker search would not work.There have been no functional changes in ColReorder since the 3.0.0-beta.1 release. For a full description of the changes in this major release since the last non-beta release, please refer to the beta's release notes:
There are a number of reasons for doing this:
This is a backwards compatible change - the original files are now no-op files and can be included with no ill effect. They shouldn't be included for new projects, but old projects can continue to use them with no issues and they can be dropped as developer time allows.
For a full description of the changes in this major release since the last non-beta release, please refer also to the previous release notes:
orderCol and columnOrder button types to provide control over the table ordering via buttons.