ENH Remove unused Translatable code

This commit is contained in:
Steve Boyd 2023-01-17 14:42:40 +13:00
parent 8ad2e5d9fb
commit 1a59bf50d1
4 changed files with 3 additions and 7 deletions

View File

@ -157,7 +157,7 @@ trait Extensible
* @see http://doc.silverstripe.org/framework/en/trunk/reference/dataextension
* @param string $classOrExtension Class that should be extended - has to be a subclass of {@link Object}
* @param string $extension Subclass of {@link Extension} with optional parameters
* as a string, e.g. "Versioned" or "Translatable('Param')"
* as a string, e.g. "Versioned"
* @return bool Flag if the extension was added
*/
public static function add_extension($classOrExtension, $extension = null)

View File

@ -331,7 +331,7 @@ class DataQuery
"RecordClassName"
);
// TODO: Versioned, Translatable, SiteTreeSubsites, etc, could probably be better implemented as subclasses
// TODO: Versioned, SiteTreeSubsites, etc, could probably be better implemented as subclasses
// of DataQuery
$obj = Injector::inst()->get($this->dataClass);

View File

@ -5,7 +5,7 @@ namespace SilverStripe\ORM\FieldType;
use SilverStripe\i18n\i18n;
/**
* Locale database field, mainly used in {@link Translatable} extension.
* Locale database field
*
* @todo Allowing showing locale values in different languages through Nice()
*/

View File

@ -14,8 +14,6 @@ use InvalidArgumentException;
/**
* Base-class for storage and retrieval of translated entities.
*
* Please see the 'translatable' module for managing translations of database-content.
*
* <b>Usage</b>
*
* PHP:
@ -37,8 +35,6 @@ use InvalidArgumentException;
* </code>
*
* File-based i18n-translations always have a "locale" (e.g. 'en_US').
* Common language names (e.g. 'en') are mainly used in the 'translatable' module
* database-entities.
*
* <b>Text Collection</b>
*