Give the gift of Drupal. All merchandise is 50% off through 2016.
Currently there is no standard way to document additional entity information provided by modules. As a consequence when the Content Translation module was added to core, all its specific entity information properties were documented in the
ContentTranslationControllerInterface (which does not feel the right place) and in part in the
@EntityType annotation, even if those are not supposed to be declared nor documented there, as contrib modules won't be able to do it. Moreover code in
core/lib should have no knowledge of code in
core/modules so this is plain wrong anyway.
- Remove the CT entity info keys from the
- Move the actual documentation in a place where people will actually find it, that is as a docblock in the
- Adopt this as an official documentation policy.
Documentation team review RTBC
User interface changes
Original report by tim.plunkett
As I discovered in, there are at least a half dozen properties in the annotation that are only used by translation_entity module.
The only properties in there should be for stuff relevant to \Drupal\Core.
Contrib modules will also likely want to tack on their own properties to the EntityType annotation, and translation_entity can serve as an example of how to do that.