Details
-
Story
-
Resolution: Unresolved
-
Medium
-
None
-
None
-
None
Description
Descriptions of content types and their field definitions is right now hardcoded to eng-GB. For a repository that doesn't use that language, no error will occur, but they will all be empty.
That part should be improved so that the actual language descriptions exist for is used. It could be by default the repository's most prioritized language for the admin, with an explicit option for edge cases.
src/Schema/Domain/Content/Worker/ContentType/AddContentOfTypeConnectionToDomainGroup.php: 'description' => isset($descriptions['eng-GB']) ? $descriptions['eng-GB'] : 'No description available', src/Schema/Domain/Content/Worker/ContentType/AddContentTypeToContentTypeIdentifierList.php: $description = isset($descriptions['eng-GB']) ? $descriptions['eng-GB'] : 'No description available'; src/Schema/Domain/Content/Worker/ContentType/AddDomainContentToDomainGroup.php: 'description' => isset($descriptions['eng-GB']) ? $descriptions['eng-GB'] : 'No description available', src/Schema/Domain/Content/Worker/ContentTypeGroup/AddDomainGroupToDomain.php: 'description' => $contentTypeGroup->getDescription('eng-GB'), src/Schema/Domain/Content/Worker/FieldDefinition/AddFieldDefinitionToDomainContentType.php: $description = $args['FieldDefinition']->getDescription('eng-GB') ?? '';