Actions
Story #84916
closedEpic #83932: Initiative: Datahandler & Persistence
Epic #84914: Streamline entity configuration layer
Provide generic entity relationship model
Status:
Closed
Priority:
Should have
Assignee:
-
Category:
-
Target version:
-
Start date:
2018-05-03
Due date:
% Done:
0%
Estimated time:
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).
Updated by Benni Mack about 2 months ago
- Related to Feature #104002: Schema API added
Updated by Benni Mack about 2 months ago
- Status changed from New to Closed
Finally implemented via #104002
Actions