MINOR Warning about imminent TableField deprecation

This commit is contained in:
Ingo Schommer 2012-03-15 22:31:27 +01:00
parent e443ec5c9c
commit 22dc7fd2d8
2 changed files with 3 additions and 1 deletions

View File

@ -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

View File

@ -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