Contrib.social

[META] Keep track of DataTables library versions an its move away from jQuery

Open on Drupal.org →
Created on 13 September 2018, almost 6 years ago
Updated 7 February 2024, 5 months ago

This is the META issue to keep track of the DataTables plugin library updates which need to get implemented in the DataTables implementation Drupal module. D8 patches first please, backports D7 need to be discussed. It will also track the shift of JQuery fading from DataTables. https://datatables.net/examples/non_jquery/init.html

I started this issue to prevent more clutter and to close the forked efforts here in the issue queue. Some issues have been started creating own branches of the implementation and with mixed code, parts of the original code with new parts and new features or mixed code with changes in the original library and mixed quality regarding the Drupal coding standards. This way it is impossible to keep track of changes or new upcoming errors. Especially without any discussion about IF WE want to modify the original library code (which is not recommended since we can't know if the library keeps its MIT license in future). We can't merge code this way. We need to split the different actions and need to patch them step by step against the existing branches. Please join here, if you are interested in this plan (library update support).

To show our users and contributors that the maintainers are willing to push the DataTables implementation Drupal module to its next level and that we need a smart idea how we can easily keep track of the quite frequently jQuery library updates and how to support them in the module we need a META issue. This is the one.

Feel free to post ideas or points to discuss or library update patches against the latest 8.x- dev. But please let's split features! This issue is ONLY for keeping track of DataTable library updates and its implementation in the Drupal module. No other features should be added in patches here. We will link other issues here, where new features are build.

EDIT: Apart from that -> 📌 New DataTables Slack channel to discuss changes & progess and quick reach out. Active

📌 Task
Status

Needs review

Version

2.0

Component

Code

Created by

🇩🇪Germany diqidoq Berlin | Hamburg | New York | London | Paris

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

Not all content is available!

It's likely this issue predates Contrib.social: some issue and comment data are missing.

  • Status changed to Needs review over 1 year ago
  • Comment about 1 year ago →
    🇫🇷France Chris64 France

    Here a patch for the README.txt file with explanations about jQuery DataTables plugin library update to version 1.10.x with composer. For use with Drupal 10 the patch from 3332040 📌 Drupal core has changed jQuery once() [Drupal 10 compatibility] Fixed is assumed applied.

  • Comment about 1 year ago →
    🇩🇪Germany diqidoq Berlin | Hamburg | New York | London | Paris

    Again: Awesome work and clarification on the order of things @Chris64, Great work! +1 will review & commit asap.

  • Comment 9 months ago →
    🇫🇷France Chris64 France

    New release with this patch: see https://www.drupal.org/project/datatables/issues/3332040 📌 Drupal core has changed jQuery once() [Drupal 10 compatibility] Fixed .

  • Comment 9 months ago →
    🇩🇪Germany diqidoq Berlin | Hamburg | New York | London | Paris

    There is a chance that DataTables moves gradually away from jQuery or runs more and more parallel projects. It was a long road and long discussion with reasonable and worth to read comments of Allen regarding its long holding use of jQuery until end of 2022. But it looks like there is a mind change. Edited the title regarding this. Back read here if you are interested in his well layout thoughts why still jQuery for so long:

    https://datatables.net/forums/discussion/51702/non-jquery-version-of-dat...

    We should follow this (I do for years) since Drupal dropped jQuery, Bootstrap dropped jQuery and it more and more becomes a unnecessary weight in dependencies. I am free of opinionated positions to jQuery. I think its not smart to follow each horse immediately. But over the years jQuery became more and more incompatible with other (newer) developments in JS. And additionally: it was different when many depend on the same. But when DataTables and 1or 2 others are the only ones, then it becomes a shift in direction of unbalanced ballast. So it is not a trend following but a final reasonably conclusion.

    Read about examples of DataTables without jQuery in progress here for example: https://datatables.net/examples/non_jquery/init.html

    And your thoughts are welcome here. Its a META.

  • Comment 9 months ago →
    🇩🇪Germany diqidoq Berlin | Hamburg | New York | London | Paris
  • Comment 9 months ago →
    🇩🇪Germany diqidoq Berlin | Hamburg | New York | London | Paris
  • Comment 5 months ago →
    🇩🇪Germany diqidoq Berlin | Hamburg | New York | London | Paris

    Good news. Drupal will keep jQuery in core, at least in 10 and 11 so we are not in a hurry here ;-)

contrib.social Blog FAQ Discussions
Production build 0.69.0 2024