Skip to content
This repository
Browse code

MINOR Warning about imminent TableField deprecation

  • Loading branch information...
commit 22dc7fd2d8506a8b660f5c3b428327b90e801582 1 parent e443ec5
Ingo Schommer authored March 15, 2012
1  docs/en/changelogs/3.0.0.md
Source Rendered
@@ -122,6 +122,7 @@ It's a substantial rewrite of the features previously captured by `TableListFiel
122 122
 The legacy fields remain operational for now, although a switch to `GridField` is strongly encouraged,
123 123
 for stability, interface and performance reasons. The `HasManyComplexTableField` and `ManyManyComplexTableField`
124 124
 are no longer maintained, for those you do have to make the switch.
  125
+The `TableField` class will be deprecated soon, but we don't have an adequate replacement for it yet.
125 126
 
126 127
 Upgrade example: Record listing
127 128
 
3  forms/TableField.php
@@ -10,7 +10,8 @@
10 10
  * A TableField-instance should never be saved twice without reloading, because otherwise it 
11 11
  * can't determine if a field is new (=create) or existing (=update), and will produce duplicates.
12 12
  * 
13  
- * @todo We should refactor this to support a single FieldList instead of evaluated Strings for building FormFields
  13
+ * IMPORTANT: This class is about to be deprecated in favour of a new GridFieldEditableColumns component,
  14
+ * see http://open.silverstripe.org/ticket/7045
14 15
  * 
15 16
  * @package forms
16 17
  * @subpackage fields-relational

0 notes on commit 22dc7fd

Please sign in to comment.
Something went wrong with that request. Please try again.