D8 port (from the existing 7.x-3.x to a new 8.x-3.x)

Here's a first WIP sandbox of the Drupal 8 version.

Is not working 100% but was a nice start :)

Here's the Sandbox: https://www.drupal.org/sandbox/sebas5384/2311397

And the authors:
Walmyr:
--author="wlsf82 <wlsf82@2914625.no-reply.drupal.org>"

Felipe:
--author="felipeduardo <felipeduardo@1232108.no-reply.drupal.org>"

Sebas:
--author="sebas5384 <sebas5384@567694.no-reply.drupal.org>"

Cheers!,
Sebas.

Here's to catch up the issue with existing commits.

There is now a dev branch for 8.x-2.x which started by refactoring work done in the sandbox project. A big part of that effort was sponsored by Wunderkraut and the rest I did in my own time.

dev version released, so closing this issue.

https://www.drupal.org/node/2653518

Upgrade path has not been tested therefore for now an alpha release would be most appropriate. See https://www.drupal.org/node/1015226.

Created an 8.x-2.0-alpha1 tag.

Re-opening as (with time) we would also need to port 7.x-3.x.

Port 7.x-3.x features to a new 8.x-3.x version (to be created).

Title change to cover the changed objective of the issue.

Is there still a need for a 3.x branch? What would the difference be? 2.x seems quite popular already.

New features in the 7.x-3.x branch (not in D8 yet)

• Display related settings have been moved from 'manage fields' to 'manage display' to differ the display of the same field per content type.
• Offers 'Raw Data (JSON)' format besides 'Tabular View'. For use with Views Datasource apply the latest patch on it of #2468325: For nesting JSON structures, allow certain fields to be designated for "raw passthrough".
• The table content can now be indexed with the Search API.
• Remove all empty columns and rows instead of only the trailing ones.
• Hide a column if every corresponding row is empty (excluding header).
• Make it possible to disable sticky table headers.
• CSV import now working with non-UTF8 encoded files.
• Allow to have the first column as header instead of first row (vertical).
• Support for Tablesorter.
• XML output.
• Allow linebreaks (textarea).
• Support for Multiple Fields Remove Button.
• Optionally themeless output of a node's tablefield on the path 'node/%/themeless' (HTML, JSON or XML). In that case add Disallow: */themeless in the robots.txt file.
• Configurable maxlength.
• Make striping (odd/even class) optional.
• Other modules are now able to override the output of the tablefield.
• Ability to hide or disable the import CSV option.

Please help by porting above features to D8. We always commit with attribution to the patch author.

Yes, I saw that, but could we simply add these features to the 2.x branch, or is the technical design too different?

I gave it some thought. IMHO it makes more sense to keep feature parity between the same branches on D7 and D8 without blocking new releases on the 2.x branch.

That means that if the features mentioned in #12 do get into D8, we should open the 8.x-3.x branch for it. In D7 the database structure has changed between the 2.x and the 3.x branch. That means also database update hooks in the install file are needed. That was then the reason to bump up the branch number from 2 to 3. For D8 the same logic applies.

Most of the related issues that have led to the 3.x branch can be found on the release notes. It might be helpful to borrow some of the code found in the patches of the issues to reach feature parity of the D8 version of the Tablefield module.

• https://www.drupal.org/project/tablefield/releases/7.x-3.0
• https://www.drupal.org/project/tablefield/releases/7.x-3.1
• https://www.drupal.org/project/tablefield/releases/7.x-3.2

Feel also free to reopen the issues found there, mark them with a 8.x-3.x version (to be created) and give them the status "Patch (to be ported)". That is better than opening new issues as others would likely miss out on the information that led to the D7 feature that might be useful for D8 as well.

Best strategy when working on these features is to:

• start a D7 sandbox at https://simplytest.me/project/tablefield/7.x-3.x
• add a tablefield to a content type at ../admin/structure/types/manage/page/fields
• make some test table as content on a node
• check the different options on the "Manage display" settings at ../admin/structure/types/manage/page/display.

Should we create new issues for each one?
Should we update the project page to link each feature to the respective issues so folks can know where to help out?

4.x might make more sense at this point so it's not tied to D8 specifically.