Do a rewrite of the module

Problem/Motivation

After examining the actual 3.0.x codebase (using AI analyses), a rewrite is strongly justified. The code reveals significant technical debt accumulated across multiple Drupal version migrations, with complex data handling, fragile state management, and architectural patterns that don't align with modern Drupal best practices.

Key Finding: The data storage format uses PHP's native serialize() with blob storage, NOT JSON . This is a major migration consideration. In other words, it will be hard to provide an upgrade path. When we release a future version, it should bump up to a 4.0.x version.

Proposed resolution

See the Development Roadmap in the attached Tablefield 3.0.x Code Analysis.

Related AI chat session

See https://claude.ai/share/3933400e-283a-4ef0-acc5-21ea4904e841