Browse files

MINOR Warning about imminent TableField deprecation

  • Loading branch information...
1 parent e443ec5 commit 22dc7fd2d8506a8b660f5c3b428327b90e801582 @chillu chillu committed Mar 15, 2012
Showing with 3 additions and 1 deletion.
  1. +1 −0 docs/en/changelogs/
  2. +2 −1 forms/TableField.php
@@ -122,6 +122,7 @@ It's a substantial rewrite of the features previously captured by `TableListFiel
The legacy fields remain operational for now, although a switch to `GridField` is strongly encouraged,
for stability, interface and performance reasons. The `HasManyComplexTableField` and `ManyManyComplexTableField`
are no longer maintained, for those you do have to make the switch.
+The `TableField` class will be deprecated soon, but we don't have an adequate replacement for it yet.
Upgrade example: Record listing
@@ -10,7 +10,8 @@
* A TableField-instance should never be saved twice without reloading, because otherwise it
* can't determine if a field is new (=create) or existing (=update), and will produce duplicates.
- * @todo We should refactor this to support a single FieldList instead of evaluated Strings for building FormFields
+ * IMPORTANT: This class is about to be deprecated in favour of a new GridFieldEditableColumns component,
+ * see
* @package forms
* @subpackage fields-relational

0 comments on commit 22dc7fd

Please sign in to comment.