From 22dc7fd2d8506a8b660f5c3b428327b90e801582 Mon Sep 17 00:00:00 2001 From: Ingo Schommer Date: Thu, 15 Mar 2012 22:31:27 +0100 Subject: [PATCH] MINOR Warning about imminent TableField deprecation --- docs/en/changelogs/3.0.0.md | 1 + forms/TableField.php | 3 ++- 2 files changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/en/changelogs/3.0.0.md b/docs/en/changelogs/3.0.0.md index 3b71fcbbf..bc84a8bea 100644 --- a/docs/en/changelogs/3.0.0.md +++ b/docs/en/changelogs/3.0.0.md @@ -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 diff --git a/forms/TableField.php b/forms/TableField.php index 2f4a79ea9..89e20c15c 100644 --- a/forms/TableField.php +++ b/forms/TableField.php @@ -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 http://open.silverstripe.org/ticket/7045 * * @package forms * @subpackage fields-relational