Story #84916

Epic #83932: Initiative: Datahandler & Persistence

Epic #84914: Streamline entity configuration layer

Provide generic entity relationship model

Added by Oliver Hader about 1 year ago. Updated about 1 year ago.

Status:
New
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2018-05-03
Due date:
% Done:

0%

TYPO3 Version:
9
PHP Version:
Tags:
Sprint Focus:

Description

Expected goal

$contentSchemaDefinition = (new SomeService)->getSchemaDefinition('tt_content');
$fileReferenceSchemaDefinition = (new SomeService)->getSchemaDefinition('sys_file_reference');
var_dump($contentSchemaDefinition->getProperty('media')->getRelations());
var_dump($fileReferenceSchemaDefinition->getProperty('uid_foreign')->getRelations());

might output something like

# relations for tt_content.media
+ ActiveRelation: schemaName "sys_file_reference" 
# relations for sys_file_reference.uid_foreign
+ PassiveRelation: schemaName "tt_content", propertyName: "image" 
+ PassiveRelation: schemaName "tt_content", propertyName: "media" 
+ PassiveRelation: schemaName "tt_content", propertyName: "assets" 

Currently the "opposite usage" for relations is not explicitly known. In order to enhance look ups this information should be cached along with the plain schema definition (e.g. TCA).

History

#1 Updated by Oliver Hader about 1 year ago

  • Description updated (diff)

Also available in: Atom PDF