77518[FEATURE] Content Blocks Backend API
Commit message
Review
-
Code review CR 0
-
Verified V 0
Issues 1
Files 226
- typo3/sysext/content_blocks/Classes/Backend/Preview/PreviewRenderer.phpnew+79 −0
- typo3/sysext/content_blocks/Classes/Basics/BasicsLoader.phpnew+55 −0
- typo3/sysext/content_blocks/Classes/Basics/BasicsRegistry.phpnew+54 −0
- typo3/sysext/content_blocks/Classes/Basics/BasicsService.phpnew+83 −0
- typo3/sysext/content_blocks/Classes/Basics/LoadedBasic.phpnew+56 −0
- typo3/sysext/content_blocks/Classes/Builder/ContentBlockConfiguration.phpnew+58 −0
- typo3/sysext/content_blocks/Classes/Builder/ContentBlockSkeletonBuilder.phpnew+152 −0
- typo3/sysext/content_blocks/Classes/Command/CreateContentBlockCommand.phpnew+209 −0
- typo3/sysext/content_blocks/Classes/Command/PackageResolver.phpnew+75 −0
- typo3/sysext/content_blocks/Classes/DataProcessing/ContentBlocksDataProcessor.phpnew+60 −0
- typo3/sysext/content_blocks/Classes/DataProcessing/RelationResolver.phpnew+240 −0
- typo3/sysext/content_blocks/Classes/Definition/Factory/Struct/ProcessedContentType.phpnew+33 −0
- typo3/sysext/content_blocks/Classes/Definition/Factory/Struct/ProcessedFieldsResult.phpnew+34 −0
- typo3/sysext/content_blocks/Classes/Definition/Factory/Struct/ProcessedTableDefinition.phpnew+31 −0
- typo3/sysext/content_blocks/Classes/Definition/Factory/Struct/ProcessingInput.phpnew+62 −0
- typo3/sysext/content_blocks/Classes/Definition/Factory/ContentTypeFactory.phpnew+47 −0
- typo3/sysext/content_blocks/Classes/Definition/Factory/TableDefinitionCollectionFactory.phpnew+518 −0
- typo3/sysext/content_blocks/Classes/Definition/ContentElementDefinition.phpnew+138 −0
- typo3/sysext/content_blocks/Classes/Definition/ContentType.phpnew+55 −0
- typo3/sysext/content_blocks/Classes/Definition/ContentTypeDefinition.phpnew+214 −0
Show 206 more files
- typo3/sysext/content_blocks/Classes/Definition/ContentTypeInterface.phpnew+38 −0
- typo3/sysext/content_blocks/Classes/Definition/LanguagePath.phpnew+50 −0
- typo3/sysext/content_blocks/Classes/Definition/PageTypeDefinition.phpnew+49 −0
- typo3/sysext/content_blocks/Classes/Definition/PaletteDefinition.phpnew+66 −0
- typo3/sysext/content_blocks/Classes/Definition/PaletteDefinitionCollection.phpnew+73 −0
- typo3/sysext/content_blocks/Classes/Definition/RecordTypeDefinition.phpnew+49 −0
- typo3/sysext/content_blocks/Classes/Definition/SqlColumnDefinition.phpnew+56 −0
- typo3/sysext/content_blocks/Classes/Definition/SqlDefinition.phpnew+77 −0
- typo3/sysext/content_blocks/Classes/Definition/TableDefinition.phpnew+171 −0
- typo3/sysext/content_blocks/Classes/Definition/TableDefinitionCollection.phpnew+68 −0
- typo3/sysext/content_blocks/Classes/Definition/TcaColumnsDefinition.phpnew+79 −0
- typo3/sysext/content_blocks/Classes/Definition/TcaFieldDefinition.phpnew+153 −0
- typo3/sysext/content_blocks/Classes/Definition/TypeDefinitionCollection.phpnew+88 −0
- typo3/sysext/content_blocks/Classes/Definition/TypeResolver.phpnew+54 −0
- typo3/sysext/content_blocks/Classes/DependencyInjection/LoaderPass.phpnew+56 −0
- typo3/sysext/content_blocks/Classes/Enumeration/FieldType.phpnew+135 −0
- typo3/sysext/content_blocks/Classes/Enumeration/FlexFormSubType.phpnew+27 −0
- typo3/sysext/content_blocks/Classes/Event/AfterContentBlocksTcaCompilationEvent.phpnew+36 −0
- typo3/sysext/content_blocks/Classes/FieldConfiguration/CategoryFieldConfiguration.phpnew+99 −0
- typo3/sysext/content_blocks/Classes/FieldConfiguration/CheckboxFieldConfiguration.phpnew+106 −0
- typo3/sysext/content_blocks/Classes/FieldConfiguration/CollectionFieldConfiguration.phpnew+185 −0
- typo3/sysext/content_blocks/Classes/FieldConfiguration/ColorFieldConfiguration.phpnew+112 −0
- typo3/sysext/content_blocks/Classes/FieldConfiguration/DateTimeFieldConfiguration.phpnew+141 −0
- typo3/sysext/content_blocks/Classes/FieldConfiguration/EmailFieldConfiguration.phpnew+116 −0
- typo3/sysext/content_blocks/Classes/FieldConfiguration/FieldConfigurationInterface.phpnew+31 −0
- typo3/sysext/content_blocks/Classes/FieldConfiguration/FileFieldConfiguration.phpnew+124 −0
- typo3/sysext/content_blocks/Classes/FieldConfiguration/FlexFormFieldConfiguration.phpnew+61 −0
- typo3/sysext/content_blocks/Classes/FieldConfiguration/FolderFieldConfiguration.phpnew+113 −0
- typo3/sysext/content_blocks/Classes/FieldConfiguration/LanguageFieldConfiguration.phpnew+50 −0
- typo3/sysext/content_blocks/Classes/FieldConfiguration/LinebreakFieldConfiguration.phpnew+48 −0
- typo3/sysext/content_blocks/Classes/FieldConfiguration/LinkFieldConfiguration.phpnew+122 −0
- typo3/sysext/content_blocks/Classes/FieldConfiguration/NumberFieldConfiguration.phpnew+132 −0
- typo3/sysext/content_blocks/Classes/FieldConfiguration/PaletteFieldConfiguration.phpnew+48 −0
- typo3/sysext/content_blocks/Classes/FieldConfiguration/RadioFieldConfiguration.phpnew+84 −0
- typo3/sysext/content_blocks/Classes/FieldConfiguration/ReferenceFieldConfiguration.phpnew+184 −0
- typo3/sysext/content_blocks/Classes/FieldConfiguration/SelectFieldConfiguration.phpnew+208 −0
- typo3/sysext/content_blocks/Classes/FieldConfiguration/TabFieldConfiguration.phpnew+48 −0
- typo3/sysext/content_blocks/Classes/FieldConfiguration/TextareaFieldConfiguration.phpnew+146 −0
- typo3/sysext/content_blocks/Classes/FieldConfiguration/TextFieldConfiguration.phpnew+128 −0
- typo3/sysext/content_blocks/Classes/FieldConfiguration/WithCommonProperties.phpnew+73 −0
- typo3/sysext/content_blocks/Classes/Generator/HtmlTemplateCodeGenerator.phpnew+43 −0
- typo3/sysext/content_blocks/Classes/Generator/IconGenerator.phpnew+47 −0
- typo3/sysext/content_blocks/Classes/Generator/PageTsConfigGenerator.phpnew+67 −0
- typo3/sysext/content_blocks/Classes/Generator/PageTypeGenerator.phpnew+48 −0
- typo3/sysext/content_blocks/Classes/Generator/SqlGenerator.phpnew+57 −0
- typo3/sysext/content_blocks/Classes/Generator/TcaGenerator.phpnew+660 −0
- typo3/sysext/content_blocks/Classes/Generator/TypoScriptGenerator.phpnew+72 −0
- typo3/sysext/content_blocks/Classes/Generator/UserTsConfigGenerator.phpnew+50 −0
- typo3/sysext/content_blocks/Classes/Loader/ContentBlockLoader.phpnew+231 −0
- typo3/sysext/content_blocks/Classes/Loader/LoadedContentBlock.phpnew+98 −0
- typo3/sysext/content_blocks/Classes/Loader/LoaderFactory.phpnew+46 −0
- typo3/sysext/content_blocks/Classes/Loader/LoaderInterface.phpnew+28 −0
- typo3/sysext/content_blocks/Classes/Registry/ContentBlockRegistry.phpnew+55 −0
- typo3/sysext/content_blocks/Classes/Registry/LanguageFileRegistry.phpnew+52 −0
- typo3/sysext/content_blocks/Classes/Registry/LanguageFileRegistryInterface.phpnew+29 −0
- typo3/sysext/content_blocks/Classes/Service/TypeDefinitionLabelService.phpnew+52 −0
- typo3/sysext/content_blocks/Classes/Utility/ContentBlockPathUtility.phpnew+156 −0
- typo3/sysext/content_blocks/Classes/Utility/UniqueNameUtility.phpnew+36 −0
- typo3/sysext/content_blocks/Classes/Validation/PageTypeNameValidator.phpnew+60 −0
- typo3/sysext/content_blocks/Classes/ViewHelpers/Asset/CssViewHelper.phpnew+142 −0
- typo3/sysext/content_blocks/Classes/ViewHelpers/Asset/ScriptViewHelper.phpnew+141 −0
- typo3/sysext/content_blocks/Classes/ViewHelpers/TranslateViewHelper.phpnew+85 −0
- typo3/sysext/content_blocks/Configuration/Icons.phpnew+8 −0
- typo3/sysext/content_blocks/Configuration/Services.phpnew+13 −0
- typo3/sysext/content_blocks/Configuration/Services.yamlnew+92 −0
- typo3/sysext/content_blocks/ContentBlocks/Basics/Appearance.yamlnew+24 −0
- typo3/sysext/content_blocks/ContentBlocks/Basics/Categories.yamlnew+10 −0
- typo3/sysext/content_blocks/ContentBlocks/Basics/Links.yamlnew+13 −0
- typo3/sysext/content_blocks/Documentation/FAQ/Index.rstnew+79 −0
- typo3/sysext/content_blocks/Documentation/History/Index.rstnew+209 −0
- typo3/sysext/content_blocks/Documentation/Installation/Index.rstnew+15 −0
- typo3/sysext/content_blocks/Documentation/IntegratorManual/Basics/Index.rstnew+75 −0
- typo3/sysext/content_blocks/Documentation/IntegratorManual/ContentBlockDefinition/Index.rstnew+93 −0
- typo3/sysext/content_blocks/Documentation/IntegratorManual/ContentBlockSkeleton/Index.rstnew+62 −0
- typo3/sysext/content_blocks/Documentation/IntegratorManual/ExtendContentBlockTCA/Index.rstnew+53 −0
- typo3/sysext/content_blocks/Documentation/IntegratorManual/Installation/Index.rstnew+20 −0
- typo3/sysext/content_blocks/Documentation/IntegratorManual/ParseFunc/Index.rst3new+22 −0
- typo3/sysext/content_blocks/Documentation/IntegratorManual/ReuseExistingFields/Index.rstnew+81 −0
- typo3/sysext/content_blocks/Documentation/IntegratorManual/Templating/Index.rstnew+121 −0
- typo3/sysext/content_blocks/Documentation/IntegratorManual/YamlReference/Basic/Index.rstnew+23 −0
- typo3/sysext/content_blocks/Documentation/IntegratorManual/YamlReference/Category/Index.rstnew+84 −0
- typo3/sysext/content_blocks/Documentation/IntegratorManual/YamlReference/Checkbox/Index.rstnew+92 −0
- typo3/sysext/content_blocks/Documentation/IntegratorManual/YamlReference/Collection/Index.rstnew+158 −0
- typo3/sysext/content_blocks/Documentation/IntegratorManual/YamlReference/Color/Index.rstnew+95 −0
- typo3/sysext/content_blocks/Documentation/IntegratorManual/YamlReference/DateTime/Index.rstnew+112 −0
- typo3/sysext/content_blocks/Documentation/IntegratorManual/YamlReference/Email/Index.rstnew+74 −0
- typo3/sysext/content_blocks/Documentation/IntegratorManual/YamlReference/File/Index.rstnew+85 −0
- typo3/sysext/content_blocks/Documentation/IntegratorManual/YamlReference/FlexForm/Index.rstnew+157 −0
- typo3/sysext/content_blocks/Documentation/IntegratorManual/YamlReference/Folder/Index.rstnew+85 −0
- typo3/sysext/content_blocks/Documentation/IntegratorManual/YamlReference/Linebreak/Index.rstnew+33 −0
- typo3/sysext/content_blocks/Documentation/IntegratorManual/YamlReference/Link/Index.rstnew+84 −0
- typo3/sysext/content_blocks/Documentation/IntegratorManual/YamlReference/Number/Index.rstnew+132 −0
- typo3/sysext/content_blocks/Documentation/IntegratorManual/YamlReference/Palette/Index.rstnew+36 −0
- typo3/sysext/content_blocks/Documentation/IntegratorManual/YamlReference/Radio/Index.rstnew+86 −0
- typo3/sysext/content_blocks/Documentation/IntegratorManual/YamlReference/Reference/Index.rstnew+78 −0
- typo3/sysext/content_blocks/Documentation/IntegratorManual/YamlReference/Select/Index.rstnew+182 −0
- typo3/sysext/content_blocks/Documentation/IntegratorManual/YamlReference/Tab/Index.rstnew+36 −0
- typo3/sysext/content_blocks/Documentation/IntegratorManual/YamlReference/Text/Index.rstnew+126 −0
- typo3/sysext/content_blocks/Documentation/IntegratorManual/YamlReference/Textarea/Index.rstnew+114 −0
- typo3/sysext/content_blocks/Documentation/IntegratorManual/YamlReference/Index.rst4new+195 −0
- typo3/sysext/content_blocks/Documentation/IntegratorManual/Index.rstnew+25 −0
- typo3/sysext/content_blocks/Documentation/Introduction/Index.rstnew+28 −0
- typo3/sysext/content_blocks/Documentation/KnownProblems/Index.rstnew+38 −0
- typo3/sysext/content_blocks/Documentation/genindex.rstnew+7 −0
- typo3/sysext/content_blocks/Documentation/Includes.rst.txtnew+33 −0
- typo3/sysext/content_blocks/Documentation/Index.rstnew+56 −0
- typo3/sysext/content_blocks/Documentation/Settings.cfgnew+30 −0
- typo3/sysext/content_blocks/Documentation/Sitemap.rstnew+9 −0
- typo3/sysext/content_blocks/Resources/Private/Language/locallang.xlfnew+11 −0
- typo3/sysext/content_blocks/Resources/Public/Icons/ContentBlockIcon.svgnew+1 −0
- typo3/sysext/content_blocks/Resources/Public/Icons/Extension.svgnew+1 −0
- typo3/sysext/content_blocks/Tests/Fixtures/DataSet/category_many_to_many.csvnew+16 −0
- typo3/sysext/content_blocks/Tests/Fixtures/DataSet/category_one_to_many.csvnew+4 −0
- typo3/sysext/content_blocks/Tests/Fixtures/DataSet/category_one_to_one.csvnew+4 −0
- typo3/sysext/content_blocks/Tests/Fixtures/DataSet/collections.csvnew+10 −0
- typo3/sysext/content_blocks/Tests/Fixtures/DataSet/collections_recursive.csvnew+8 −0
- typo3/sysext/content_blocks/Tests/Fixtures/DataSet/db_reference.csvnew+11 −0
- typo3/sysext/content_blocks/Tests/Fixtures/DataSet/db_reference_hidden.csvnew+10 −0
- typo3/sysext/content_blocks/Tests/Fixtures/DataSet/db_reference_mm.csvnew+8 −0
- typo3/sysext/content_blocks/Tests/Fixtures/DataSet/db_reference_multiple.csvnew+8 −0
- typo3/sysext/content_blocks/Tests/Fixtures/DataSet/file_reference.csvnew+6 −0
- typo3/sysext/content_blocks/Tests/Fixtures/DataSet/folder_files.csvnew+3 −0
- typo3/sysext/content_blocks/Tests/Fixtures/DataSet/select_foreign.csvnew+4 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/bar/ContentBlocks/ContentElements/bar/Assets/ContentBlockIcon.svgnew+1 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/bar/ContentBlocks/ContentElements/bar/Assets/EditorPreview.cssnew+1 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/bar/ContentBlocks/ContentElements/bar/Assets/Frontend.cssnew+1 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/bar/ContentBlocks/ContentElements/bar/Assets/Frontend.jsnew+1 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/bar/ContentBlocks/ContentElements/bar/Source/Language/Labels.xlfnew+14 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/bar/ContentBlocks/ContentElements/bar/Source/EditorPreview.htmlnew+7 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/bar/ContentBlocks/ContentElements/bar/Source/Frontend.htmlnew+8 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/bar/ContentBlocks/ContentElements/bar/EditorInterface.yamlnew+78 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/bar/composer.jsonnew+11 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/foo/ContentBlocks/ContentElements/foo/Assets/ContentBlockIcon.svgnew+1 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/foo/ContentBlocks/ContentElements/foo/Assets/EditorPreview.cssnew+1 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/foo/ContentBlocks/ContentElements/foo/Assets/Frontend.cssnew+1 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/foo/ContentBlocks/ContentElements/foo/Assets/Frontend.jsnew+1 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/foo/ContentBlocks/ContentElements/foo/Source/Language/Labels.xlfnew+14 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/foo/ContentBlocks/ContentElements/foo/Source/EditorPreview.htmlnew+7 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/foo/ContentBlocks/ContentElements/foo/Source/Frontend.htmlnew+8 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/foo/ContentBlocks/ContentElements/foo/EditorInterface.yamlnew+90 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/foo/composer.jsonnew+11 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/simple/ContentBlocks/Basics/Simple.yamlnew+5 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/simple/ContentBlocks/ContentElements/simple/Assets/ContentBlockIcon.svgnew+1 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/simple/ContentBlocks/ContentElements/simple/Assets/EditorPreview.cssnew+1 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/simple/ContentBlocks/ContentElements/simple/Assets/Frontend.cssnew+1 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/simple/ContentBlocks/ContentElements/simple/Assets/Frontend.jsnew+1 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/simple/ContentBlocks/ContentElements/simple/Source/Language/Labels.xlfnew+14 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/simple/ContentBlocks/ContentElements/simple/Source/Frontend.htmlnew+12 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/simple/ContentBlocks/ContentElements/simple/EditorInterface.yamlnew+11 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/simple/ContentBlocks/ContentElements/simple2/Assets/ContentBlockIcon.svgnew+1 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/simple/ContentBlocks/ContentElements/simple2/Assets/EditorPreview.cssnew+1 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/simple/ContentBlocks/ContentElements/simple2/Assets/Frontend.cssnew+1 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/simple/ContentBlocks/ContentElements/simple2/Assets/Frontend.jsnew+1 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/simple/ContentBlocks/ContentElements/simple2/Source/Language/Labels.xlfnew+17 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/simple/ContentBlocks/ContentElements/simple2/Source/Frontend.htmlnew+12 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/simple/ContentBlocks/ContentElements/simple2/EditorInterface.yamlnew+26 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/simple/ContentBlocks/ContentElements/simple_with_basics/Assets/ContentBlockIcon.svgnew+1 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/simple/ContentBlocks/ContentElements/simple_with_basics/Assets/EditorPreview.cssnew+1 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/simple/ContentBlocks/ContentElements/simple_with_basics/Assets/Frontend.cssnew+1 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/simple/ContentBlocks/ContentElements/simple_with_basics/Assets/Frontend.jsnew+1 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/simple/ContentBlocks/ContentElements/simple_with_basics/Source/Language/Labels.xlfnew+14 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/simple/ContentBlocks/ContentElements/simple_with_basics/Source/Frontend.htmlnew+12 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/simple/ContentBlocks/ContentElements/simple_with_basics/EditorInterface.yamlnew+22 −0
- typo3/sysext/content_blocks/Tests/Fixtures/Extensions/simple/composer.jsonnew+11 −0
- typo3/sysext/content_blocks/Tests/Fixtures/TestFolder/sub/subfile.jpgnew+0 −0
- typo3/sysext/content_blocks/Tests/Fixtures/TestFolder/file.jpgnew+0 −0
- typo3/sysext/content_blocks/Tests/Fixtures/be_users.csvnew+4 −0
- typo3/sysext/content_blocks/Tests/Functional/DataProcessing/RelationResolverTest.phpnew+571 −0
- typo3/sysext/content_blocks/Tests/Functional/Frontend/Fixtures/frontend.csvnew+6 −0
- typo3/sysext/content_blocks/Tests/Functional/Frontend/Fixtures/frontend.typoscriptnew+6 −0
- typo3/sysext/content_blocks/Tests/Functional/Frontend/ContentBlockFrontendRenderingTest.phpnew+71 −0
- typo3/sysext/content_blocks/Tests/Functional/Generator/TcaGeneratorTest.phpnew+160 −0
- typo3/sysext/content_blocks/Tests/Functional/Registry/ContentBlockRegistryTest.phpnew+80 −0
- typo3/sysext/content_blocks/Tests/Functional/ViewHelpers/Asset/CssViewHelperTest.phpnew+67 −0
- typo3/sysext/content_blocks/Tests/Functional/ViewHelpers/Asset/ScriptViewHelperTest.phpnew+67 −0
- typo3/sysext/content_blocks/Tests/Functional/ViewHelpers/TranslateViewHelperTest.phpnew+79 −0
- typo3/sysext/content_blocks/Tests/Unit/Basics/BasicsServiceTest.phpnew+496 −0
- typo3/sysext/content_blocks/Tests/Unit/Definition/Factory/TableDefinitionCollectionFactoryTest.phpnew+1004 −0
- typo3/sysext/content_blocks/Tests/Unit/Definition/TableDefinitionCollectionTest.phpnew+146 −0
- typo3/sysext/content_blocks/Tests/Unit/FieldTypes/CategoryFieldConfigurationTest.phpnew+128 −0
- typo3/sysext/content_blocks/Tests/Unit/FieldTypes/CheckboxFieldConfigurationTest.phpnew+171 −0
- typo3/sysext/content_blocks/Tests/Unit/FieldTypes/CollectionFieldConfigurationTest.phpnew+205 −0
- typo3/sysext/content_blocks/Tests/Unit/FieldTypes/ColorFieldConfigurationTest.phpnew+144 −0
- typo3/sysext/content_blocks/Tests/Unit/FieldTypes/DateTimeFieldConfigurationTest.phpnew+231 −0
- typo3/sysext/content_blocks/Tests/Unit/FieldTypes/EmailFieldConfigurationTest.phpnew+130 −0
- typo3/sysext/content_blocks/Tests/Unit/FieldTypes/FileFieldConfigurationTest.phpnew+175 −0
- typo3/sysext/content_blocks/Tests/Unit/FieldTypes/FlexFormFieldConfigurationTest.phpnew+90 −0
- typo3/sysext/content_blocks/Tests/Unit/FieldTypes/FolderFieldConfigurationTest.phpnew+136 −0
- typo3/sysext/content_blocks/Tests/Unit/FieldTypes/LinkFieldConfigurationTest.phpnew+156 −0
- typo3/sysext/content_blocks/Tests/Unit/FieldTypes/NumberFieldConfigurationTest.phpnew+200 −0
- typo3/sysext/content_blocks/Tests/Unit/FieldTypes/RadioFieldConfigurationTest.phpnew+120 −0
- typo3/sysext/content_blocks/Tests/Unit/FieldTypes/ReferenceFieldConfigurationTest.phpnew+197 −0
- typo3/sysext/content_blocks/Tests/Unit/FieldTypes/SelectFieldConfigurationTest.phpnew+216 −0
- typo3/sysext/content_blocks/Tests/Unit/FieldTypes/TextareaFieldConfigurationTest.phpnew+162 −0
- typo3/sysext/content_blocks/Tests/Unit/FieldTypes/TextFieldConfigurationTest.phpnew+156 −0
- typo3/sysext/content_blocks/Tests/Unit/Fixtures/NoopLanguageFileRegistry.phpnew+34 −0
- typo3/sysext/content_blocks/Tests/Unit/Fixtures/TestLoader.phpnew+33 −0
- typo3/sysext/content_blocks/Tests/Unit/Generator/SqlGeneratorTest.phpnew+325 −0
- typo3/sysext/content_blocks/Tests/Unit/Generator/TcaGeneratorTest.phpnew+2009 −0
- typo3/sysext/content_blocks/Tests/Unit/Utility/UniqueNameUtilityTest.phpnew+70 −0
- typo3/sysext/content_blocks/composer.jsonnew+46 −0
- typo3/sysext/content_blocks/ext_emconf.phpnew+19 −0
- typo3/sysext/content_blocks/ext_localconf.phpnew+16 −0
- typo3/sysext/core/Documentation/Changelog/13.0/Feature-98313-ContentBlocksBackendAPI.rstnew+152 −0
- composer.json+3 −0
- composer.lock+2 −2
Review log 111194
Show 98169 earlier messages
-
Nikita Hovratov uploaded patch set 1 01/20/23, 12:32
-
core-ci voted on patch set 1 V -1 01/20/23, 12:43 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/36346
-
Nikita Hovratov uploaded patch set 2
V -101/20/23, 13:23 -
core-ci voted on patch set 2 V -1 01/20/23, 13:38 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/36350
-
Nikita Hovratov uploaded patch set 3
V -101/20/23, 13:47 -
core-ci voted on patch set 3 V -1 01/20/23, 14:21 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/36358
-
Nikita Hovratov uploaded patch set 4
V -101/20/23, 14:39 -
core-ci voted on patch set 4 V +1 01/20/23, 14:58 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/36371
-
Nikita Hovratov uploaded patch set 5
V +101/22/23, 12:35 -
core-ci voted on patch set 5 V -1 01/22/23, 12:47 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/36423
-
Nikita Hovratov uploaded patch set 6
V -101/24/23, 21:32 -
core-ci voted on patch set 6 V +1 01/24/23, 21:39 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/36585
-
Nikita Hovratov uploaded patch set 7
V +102/24/23, 14:26 -
core-ci voted on patch set 7 V +1 02/24/23, 14:52 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/38058
-
Nikita Hovratov uploaded patch set 8
V +102/24/23, 19:28 -
core-ci voted on patch set 8 V +1 02/24/23, 19:35 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/38067
-
Nikita Hovratov uploaded patch set 9
V +102/25/23, 11:51 -
core-ci voted on patch set 9 V -1 02/25/23, 12:12 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/38086
-
Nikita Hovratov uploaded patch set 10
V -102/25/23, 12:47 -
core-ci voted on patch set 10 V -1 02/25/23, 12:54 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/38089
-
Nikita Hovratov uploaded patch set 11
V -102/25/23, 12:54 -
core-ci voted on patch set 11 V +1 02/25/23, 13:02 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/38091
-
Nikita Hovratov uploaded patch set 12
V +102/25/23, 15:10 -
core-ci voted on patch set 12 V +1 02/25/23, 15:17 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/38101
-
Nikita Hovratov uploaded patch set 13
V +102/25/23, 16:51 -
core-ci voted on patch set 13 V +1 02/25/23, 16:58 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/38103
-
Nikita Hovratov uploaded patch set 14
V +102/26/23, 10:58 -
core-ci voted on patch set 14 V +1 02/26/23, 11:05 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/38111
-
Nikita Hovratov uploaded patch set 15
V +102/26/23, 13:14 -
core-ci voted on patch set 15 V +1 02/26/23, 13:21 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/38112
-
Nikita Hovratov uploaded patch set 16
V +102/26/23, 17:42 -
Nikita Hovratov uploaded patch set 17 02/26/23, 17:48
-
Nikita Hovratov uploaded patch set 18 02/26/23, 17:54
-
core-ci voted on patch set 17 V +1 02/26/23, 17:54 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/38125
-
core-ci voted on patch set 16 V +1 02/26/23, 17:59 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/38124
-
core-ci voted on patch set 18 V +1 02/26/23, 18:01 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/38126
-
Nikita Hovratov uploaded patch set 19
V +102/27/23, 09:57 -
core-ci voted on patch set 19 V -1 02/27/23, 10:33 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/38147
-
Nikita Hovratov uploaded patch set 20
V -102/27/23, 11:16 -
core-ci voted on patch set 20 V +1 02/27/23, 11:23 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/38149
-
Benni Mack commented on patch set 20 02/27/23, 15:40
-
Stefan Bürk commented on patch set 20 02/27/23, 16:43
AbstractLoader.php:36Should get a 3rd argument to the method handing over the decoded json, if not do the decoding here. E.g. LegacyLoader already reads and decodes the composer.json - could be avoided to do double decoding in that case.ComposerLoader.php:40We should avoid eventually race condition. Directly do `require()`, if `is_array()`do the if-block code, otherwise let it be generated.LegacyLoader.php:42We should avoid eventually race condition. Directly do `require()`, if `is_array()`do the if-block code, otherwise let it be generated. -
Nikita Hovratov commented on patch set 20 02/27/23, 18:04
GeneralUtility.php:29Replywill it? It's just a use statement or? I didn't want to put the Content Blocks related path stuff into the core extension, that's why I added everywhere ExtensionManagementUtility::isLoaded('content_blocks'). Not a good idea? -
Nikita Hovratov uploaded patch set 21
V +102/27/23, 18:16 -
Nikita Hovratov commented on patch set 21 02/27/23, 18:17
AbstractLoader.php:36ReplyDoneComposerLoader.php:40ReplyDoneLegacyLoader.php:42ReplyDone -
core-ci voted on patch set 21 V +1 02/27/23, 18:23 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/38166
-
Nikita Hovratov uploaded patch set 22
V +102/28/23, 08:23 -
core-ci voted on patch set 22 V +1 02/28/23, 08:30 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/38187
-
Nikita Hovratov updated the commit message in patch set 23
V +102/28/23, 11:07 -
core-ci voted on patch set 23 V +1 02/28/23, 11:15 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/38194
-
Nikita Hovratov uploaded patch set 24
V +102/28/23, 12:31 -
core-ci voted on patch set 24 V +1 02/28/23, 12:38 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/38202
-
Helmut Hummel commented on patch set 24 CR -1 02/28/23, 17:38
I haven't looked through everything, my current conclusion is the following: I like the idea of making it easier to create content elements and I appreciate the effort of working in that area. I strongly dislike the technical approach with increasing complexity by introducing yet another type of package. I might miss a lot of thoughts and decisions, but to me this seems unnecessary and could be achieved with a less complex technical concept. I would love if we'd get together and discuss those concerns.PackageArtifactBuilder.php:218Runtime API InstalledVersions should not be used in build time code. In general, I'm still reluctant to have another package type with a special handling composer wise.GeneralUtility.php:29ReplyIt won't fail, but is adds a recursive dependency. We should look for a solution that does not need thatGeneralUtility.php:2583There should be a different solution for resolving paths and handling content block packages in generalFeature-98313-ContentBlocksBackendAPI.rst:109Is this really something we want to endorse, creating individual css and js files for each content element? how would this work with a css/js build pipeline? -
Helmut Hummel commented on patch set 24 02/28/23, 17:49
Index.rst:9Not quite correct, is it?Index.rst:69see above. sql does not seem to be view related -
Benjamin Kott commented on patch set 24 03/01/23, 07:35
Feature-98313-ContentBlocksBackendAPI.rst:109ReplyContent elements need to be able to be shipped and standalone, so you can mix and match them in different installations. Having this in mind we should endorse this to have really reusable elements. Also with webcomponents in mind, this is necessary. Build project chains are in this case a thing of the past. If we take for example the bootstrap package, in an ideal world you could just use the carousel, accordion or whatever and only the resources are loaded that are necessary to achieve this. For example if bootstrap.js is already loaded, don`t load it twice. The component itself then can be adjusted through CSS variables from the main package. While we are still away having this work generally with the rise of CSS variables and JS modules a bundle for a content element is the way to go. I agree that you need to be careful with this and do not load the entire internet for a content element, but this will differentiate a good CB from a bad CB. The interesting part is here, we have no logic yet for populating general resources to the view from ajax requests, but since this is static for now, this will probably be a job for future us (on the backend side). -
Benjamin Kott commented on patch set 24 03/01/23, 07:42
Reply
Interestingly i`am on the complete opposite and prefer the version of a dedicated package type. The idea here is to have a reduced set of capabilities and feature set, to avoid mixing technologies and approaches and fully embrace a new way. We also need new ways of promoting Content Blocks and different handling in certain areas. A dedicated repository, to show capabilities and requirements. Without mixing it into the current extension handling a new package type seems the best way to go for me. Would also love to take part on that discussion. -
Simon Schaufelberger commented on patch set 24 03/01/23, 08:44
Neos has the possibility to define a "position" as well which is a ranking factor on which position the CE will be shown in the modal overlay. I think currently it all depends on the composer loader, or? See https://neos.readthedocs.io/en/stable/References/NodeTypeDefinition.html -
Helmut Hummel commented on patch set 24 03/01/23, 11:42
Reply
I'm sure there is some common ground, but from my perspective the CBs approach, as presented here, tries to address too may concerns at once, making compromises to achieve that. I think: TYPO3 needs simple and fast way to create content types (data structure + editing interface) of all kinds. Creating them should be so easy and fast, that sharing them between projects becomes irrelevant. The RENDERING of content types is a totally different pair of shoes and SHOULD be decoupled from the data structure. Each property of a content type might be rendered with an individual component. Each rendering component could be reused for rendering specific properties of different content types. (think of a headline property, present in multiple content types, vs. a headline component dealing the the rendering.) These two aspects of a "content element" as we know it now, should not (and imho can not) be tackled with a single one "CB to rule them all" approach. -
Nikita Hovratov uploaded patch set 25
CR -1V +103/01/23, 16:31 -
core-ci voted on patch set 25 V +1 03/01/23, 16:38 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/38268
-
Nikita Hovratov commented on patch set 25 03/01/23, 17:29
Reply
Yes, currently it depends on the loading order of content blocks. So you suggest to introduce an ordering with OrderingService "before:blockA", "after:blockB" ? -
Simon Schaufelberger commented on patch set 25 03/01/23, 21:05
Reply
yes please, so that grouping within a tab is possible -
Simon Schaufelberger commented on patch set 25 03/01/23, 22:15
Reply
... but on the other hand, that would add dependencies to other content blocks so my personal opinion would be to make it independent and just use an integer and then sort all CBs in the end by that. -
Claus Due commented on patch set 25 03/02/23, 02:07
General remark from here, Helmut already touched on this: Every time you write an "if extension loaded" into an EXT:core class, you are introducing a hidden cyclic dependency; a special case in core logic, designed to handle a case associated with only a single extension which depends on the core logic. This happens quite a few times throughout this merge request. It doesn't really matter that this special case is done for another core extension - it's still a hidden cyclic dependency. Suggestion instead: why not introduce events in these places which allows other packages to interact with things like resolving a path, translating a label, etc.? If you do it this way, other extensions would be able to benefit from that API to achieve similar goals - and more importantly there would be no cyclic dependencies. Of course, if you had treated "content blocks" as a typo3-cms-extension instead of inventing a new package type, then you wouldn't need this, nor would you need the composer/loader manipulation. From my perspective, this new package type adds many complications and complexity, but very little actual benefit (it basically serves as pure classification/distinction; something that could for example also be achieved with much less invasive composer metadata). I hesitate to add a -1 code review at this time but if this patch continues without addressing in particular these cyclic dependencies, I will have to vote -1. ------- Another point I'd like to raise is that in effect, this package now adds a (incomplete, partial) PHP representation on top of TCA consisting of hundreds of lines of code - when "pure" TCA could just as easily have been used. I understand the compulsion to provide a proper API for TCA, but I think we are doing ourselves a disservice by adding an incomplete/partial new API with limited support, designed for a single use case. If anyone tries to reproduce the usages of this API for their own purposes they will quickly run into trouble and start questioning why this API exists for this particular purpose, yet cannot be used for standard TCA use cases. For me personally, I would much prefer if this API was abandoned in favor of using pure TCA arrays - just like any other core package does. A future concern could then be to formalise a true and complete API to replace the huge TCA arrays, but IMHO that is far, far outside the scope of this change. -
Claus Due commented on patch set 25 03/02/23, 02:16
Reply
I fully agree with Helmut's assertions in his comment. I belive this comment was erroneously marked as "resolved" - unless you reached some resolution in private that isn't visible here. If that is the case, I would ask that you echo that resolution here. If it is not the case, I would ask that Helmut's concerns be properly addressed. For the time being, I have marked the comment as "unresolved". -
Simon Schaufelberger commented on patch set 25 03/02/23, 06:09
Index.rst:15In my opinion please don't reference links outside of the TYPO3 universe but rather use some code snippet in the documentation. -
Nikita Hovratov commented on patch set 25 03/02/23, 08:42
Reply
Hey, thanks for the hint on how to prevent the cyclic dependency. I will try that with events instead then. The distinction between extension and content-block, however, is not only cosmetical. A content-block doesn't need and shouldn't have the fully fledged functionality of an extension. This is something completely different. The only thing it needs is compatibility with resource resolving, language file translation and public resource publishing (in composer mode). For your second part, I think you haven't grasped the idea of what this should accomplish yet. This new API is targeted for newbies and frontend devs (omg it's not another tool for developers :) So writing pure TCA is out of the question here. While you technically still could use the full feature set of TCA, we promote some basic usage examples, so it looks very easy on the first glance. Polishing TCA itself is a completely other task and out of scope in this patch. -
Claus Due commented on patch set 25 03/02/23, 11:30
Reply
> Hey, thanks for the hint on how to prevent the cyclic dependency. I will try that with events instead then. YW. > The distinction between extension and content-block, however, is not only cosmetical. A content-block doesn't need and shouldn't have the fully fledged functionality of an extension. My point is: even if it only needs a sub-set of the functionality, it would get this sub-set for free (no changes to internal core code necessary), had it used the same registration approach as standard extensions. No, it doesn't *need* the full feature set of an extension, but what's the harm in *giving* it access to such by shipping and registering it the exact same way you would an extension? > For your second part, I think you haven't grasped the idea of what this should accomplish yet. No, sorry, it's you who misunderstood me (and perhaps I could have made myself clearer). The new API I'm mentioning isn't the "fields in YAML" feature. It's the set of PHP objects that were added to represent each of these fields and produce TCA array chunks. This new API consumes one type of array and produces another array. The PHP classes internally hold many of, but not all of, the properties you would use in TCA arrays. The potential confusion arises because this new API may be seen as "a way to store TCA in arbitrary/condensed formats and represent TCA with PHP objects", yet it's only purpose is to transfer and convert one type of array data (YAML source) into another (TCA source) exclusively in the context of content-blocks internals. This is why I see it as a potential problem vector. Additionally, this new format with "fields in YAML" does nothing to teach users how to actually write TCA. As such, the entry barrier that was desired to be removed, is still there (just abstracted) - and another format, albeit simpler, still has to be learned. So now instead of learning one thing, there are two things to learn. -
Nikita Hovratov commented on patch set 25 03/02/23, 12:20
Reply
> but what's the harm in giving it access to such by shipping and registering it the exact same way you would an extension? Extensions still have the limitation of having only 1 unique extension key. With content blocks it should be possible to require e.g. a vendor1/cta and vendor2/cta. They also should be loaded automatically, not installed via extension manager and not listed there either. > It's the set of PHP objects that were added to represent each of these fields and produce TCA array chunks. This is not public API, I will add @internal for these. This patch doesn't add any public PHP API, besides some events. There is currently an open patch for a TCA Schema API, but this has nothing to do with it. > Additionally, this new format with "fields in YAML" does nothing to teach users how to actually write TCA And it shouldn't :) It's true that inside `properties` it's exactly the same as TCA. The goal is to figure out the most common options that are needed and to document them, so you end up with a minimal setup. -
Helmut Hummel commented on patch set 25 03/03/23, 17:13
Reply
Preface: With TYPO3 11 extension for TYPO3 can mean it is a composer package that is *not* listed in Extension Manager and does not need to be of type "typo3-cms-extension", but still recognized by the PackageManager, thus capable of interacting with TYPO3 API. > Extensions still have the limitation of having only 1 unique extension key. With content blocks it should be possible to require e.g. a vendor1/cta and vendor2/cta. They also should be loaded automatically, not installed via extension manager and not listed there either. Here is an idea: What if the folder `Configuration/ContentBlocks/` of each extension is scanned for subfolders with content block definitions? Then some CB registry API could pick up those with *existing* API and register them automatically. Each CB can still be treated individually, paths could be resolved automatically (combining PackageManager API and CB registry API), public resources of content blocks could reside in any directory of an individual CB and still be published on Composer build time. Individuals could then still decide to publish a composer package with a single CB, but others could decide to provide a collection of CBs that depend on each other. On top of that, CBs from the composer root package could be picked up, transparently, since the root package is also a package that TYPO3 can detect as extension. The we would not need typo3conf/ContentBlocks folder any more, which would weirdly live in the legacy typo3conf folder, that does not exist any more in TYPO3 12 (Composer mode). Newly generated CBs can then be placed there and would be picked up automatically, without the need to set up some directory and a composer.json and require those in the root composer.json. At any point individual CBs can still be pulled out and published anywhere as composer package. Versioning, namespace and TYPO3 compatibility could be inherited from the composer package the CBs live in. Ordering/ Dependencies of CBs would still need to be defined explicitly, but this needed anyway as discussed above with Simon. There is still more that could be discussed, but with that idea, such technical base would require zero supporting code inside current TYPO3 core. Everything could be handled in the content_blocks extension, having concerns cleanly separated. I'm happy to learn what the flaws are in such approach (over what is proposed here) and I am also happy to explain it in more detail, in case I did not outline it clear enough. -
Nikita Hovratov uploaded patch set 26
V +103/13/23, 08:16 -
Nikita Hovratov uploaded patch set 27 03/13/23, 08:20
-
core-ci voted on patch set 27 V -1 03/13/23, 08:29 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/38858
-
core-ci voted on patch set 26 V -1 03/13/23, 08:48 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/38857
-
Nikita Hovratov uploaded patch set 28
V -103/13/23, 08:48 -
core-ci voted on patch set 28 V -1 03/13/23, 08:59 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/38859
-
Nikita Hovratov uploaded patch set 29
V -103/13/23, 09:00 -
core-ci voted on patch set 29 V -1 03/13/23, 09:07 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/38860
-
Nikita Hovratov uploaded patch set 30
V -103/13/23, 09:12 -
core-ci voted on patch set 30 V -1 03/13/23, 09:24 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/38861
-
Nikita Hovratov uploaded patch set 31
V -103/13/23, 09:29 -
core-ci voted on patch set 31 V +1 03/13/23, 09:39 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/38862
-
Nikita Hovratov uploaded patch set 32
V +103/13/23, 09:43 -
core-ci voted on patch set 32 V +1 03/13/23, 09:52 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/38867
-
Nikita Hovratov uploaded patch set 33
V +103/14/23, 09:48 -
Nikita Hovratov commented on patch set 33 03/14/23, 09:52
Reply
Content Blocks are no longer composer packages, but reside in the folder "ContentBlocks" of an extension.PackageArtifactBuilder.php:218ReplyDoneGeneralUtility.php:29ReplyDoneGeneralUtility.php:2583ReplyDoneFeature-98313-ContentBlocksBackendAPI.rst:109ReplyDone -
Nikita Hovratov commented on patch set 33 03/14/23, 09:52
Reply
Done -
core-ci voted on patch set 33 V +1 03/14/23, 09:55 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/38907
-
Nikita Hovratov commented on patch set 33 03/14/23, 12:06
Index.rst:15ReplyI think this is fine, as it is the official TYPO3 github repo. Copying the whole code snippet is contra-productive, as it will get obsolete at some point. -
Nikita Hovratov uploaded patch set 34
V +103/14/23, 12:52 -
Nikita Hovratov commented on patch set 33 03/14/23, 12:52
Index.rst:9ReplyDoneIndex.rst:69ReplyDone -
core-ci voted on patch set 34 V +1 03/14/23, 13:00 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/38922
-
Nikita Hovratov uploaded patch set 35
V +103/15/23, 16:48 -
core-ci voted on patch set 35 V +1 03/15/23, 16:55 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/38996
-
Nikita Hovratov uploaded patch set 36
V +103/15/23, 17:57 -
Nikita Hovratov commented on patch set 36 03/15/23, 17:59
Reply
Added a "priority" option. So default is the (arbitrary) loading order, which is alphabetically in most cases. If priority is set, higher values override lower ones. -
core-ci voted on patch set 36 V +1 03/15/23, 18:04 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/38999
-
Nikita Hovratov uploaded patch set 37
V +103/17/23, 12:11 -
core-ci voted on patch set 37 V -1 03/17/23, 12:49 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/39121
-
Nikita Hovratov uploaded patch set 38
V -103/17/23, 13:47 -
core-ci voted on patch set 38 V +1 03/17/23, 13:56 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/39131
-
Nikita Hovratov uploaded patch set 39
V +103/17/23, 22:12 -
core-ci voted on patch set 39 V +1 03/17/23, 22:21 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/39165
-
Nikita Hovratov uploaded patch set 40
V +103/18/23, 13:43 -
core-ci voted on patch set 40 V +1 03/18/23, 13:51 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/39187
-
Nikita Hovratov uploaded patch set 41
V +103/18/23, 20:20 -
core-ci voted on patch set 41 V +1 03/18/23, 20:27 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/39191
-
Nikita Hovratov uploaded patch set 42
V +103/19/23, 18:07 -
core-ci voted on patch set 42 V -1 03/19/23, 19:13 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/39203
-
Nikita Hovratov uploaded patch set 43
V -103/20/23, 08:13 -
core-ci voted on patch set 43 V +1 03/20/23, 08:21 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/39220
-
Andreas Kienast uploaded patch set 44
V +103/24/23, 14:36 -
core-ci voted on patch set 44 V -1 03/24/23, 15:10 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/39561
-
Nikita Hovratov uploaded patch set 45
V -103/24/23, 16:31 -
core-ci voted on patch set 45 V +1 03/24/23, 16:38 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/39575
-
Nikita Hovratov uploaded patch set 46
V +103/28/23, 10:25 -
core-ci voted on patch set 46 V +1 03/28/23, 10:40 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/39756
-
Nikita Hovratov uploaded patch set 47
V +103/31/23, 13:44 -
Nikita Hovratov commented on patch set 47 03/31/23, 13:52
Index.rst:15ReplyDone -
Nikita Hovratov uploaded patch set 48 03/31/23, 14:03
-
core-ci voted on patch set 47 V -1 03/31/23, 14:03 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/39900
-
Nikita Hovratov uploaded patch set 49 03/31/23, 14:17
-
core-ci voted on patch set 48 V -1 03/31/23, 14:29 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/39902
-
core-ci voted on patch set 49 V -1 03/31/23, 14:37 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/39903
-
Nikita Hovratov uploaded patch set 50
V -103/31/23, 15:17 -
Nikita Hovratov marked it work in progress 03/31/23, 15:17
-
core-ci voted on patch set 50 V +1 03/31/23, 15:46 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/39907
-
Nikita Hovratov uploaded patch set 51
V +105/03/23, 09:56 -
core-ci voted on patch set 51 V -1 05/03/23, 11:13 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/41512
-
Nikita Hovratov uploaded patch set 52
V -105/08/23, 10:01 -
core-ci voted on patch set 52 V -1 05/08/23, 10:04 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/41656
-
Nikita Hovratov uploaded patch set 53
V -105/08/23, 10:24 -
core-ci voted on patch set 53 V -1 05/08/23, 10:36 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/41657
-
Nikita Hovratov uploaded patch set 54
V -105/08/23, 10:47 -
core-ci voted on patch set 54 V -1 05/08/23, 11:01 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/41660
-
Nikita Hovratov uploaded patch set 55
V -105/08/23, 12:59 -
core-ci voted on patch set 55 V +1 05/08/23, 13:07 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/41663
-
Nikita Hovratov uploaded patch set 56
V +105/17/23, 16:01 -
core-ci voted on patch set 56 V -1 05/17/23, 16:03 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/41894
-
Nikita Hovratov uploaded patch set 57
V -105/17/23, 16:04 -
core-ci voted on patch set 57 V +1 05/17/23, 16:12 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/41895
-
Chris Müller uploaded patch set 58
V +105/18/23, 16:06 -
core-ci voted on patch set 58 V +1 05/18/23, 16:14 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/41907
-
Nikita Hovratov uploaded patch set 59
V +105/18/23, 18:31 -
core-ci voted on patch set 59 V -1 05/18/23, 18:47 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/41911
-
Nikita Hovratov uploaded patch set 60
V -105/20/23, 19:51 -
Nikita Hovratov uploaded patch set 61 05/20/23, 19:54
-
core-ci voted on patch set 61 V -1 05/20/23, 20:04 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/41938
-
core-ci voted on patch set 60 V -1 05/20/23, 20:05 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/41937
-
Nikita Hovratov uploaded patch set 62
V -105/21/23, 11:08 -
core-ci voted on patch set 62 V +1 05/21/23, 11:16 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/41944
-
Nikita Hovratov uploaded patch set 63
V +105/21/23, 19:03 -
core-ci voted on patch set 63 V +1 05/21/23, 19:11 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/41948
-
Nikita Hovratov uploaded patch set 64
V +105/22/23, 19:26 -
core-ci voted on patch set 64 V +1 05/22/23, 19:34 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/41960
-
Nikita Hovratov uploaded patch set 65
V +105/23/23, 09:40 -
Nikita Hovratov uploaded patch set 66 05/23/23, 09:43
-
core-ci voted on patch set 65 V -1 05/23/23, 09:49 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/41970
-
core-ci voted on patch set 66 V -1 05/23/23, 09:52 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/41971
-
Nikita Hovratov uploaded patch set 67
V -105/23/23, 09:54 -
core-ci voted on patch set 67 V +1 05/23/23, 10:02 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/41972
-
Nikita Hovratov uploaded patch set 68
V +106/09/23, 21:01 -
Nikita Hovratov uploaded patch set 69 06/09/23, 21:03
-
core-ci voted on patch set 68 V +1 06/09/23, 21:11 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/42339
-
core-ci voted on patch set 69 V +1 06/09/23, 21:11 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/42340
-
Nikita Hovratov uploaded patch set 70
V +106/19/23, 19:59 -
core-ci voted on patch set 70 V +1 06/19/23, 20:08 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/42814
-
Nikita Hovratov uploaded patch set 71
V +106/20/23, 09:34 -
core-ci voted on patch set 71 V +1 06/20/23, 09:42 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/42824
-
Nikita Hovratov uploaded patch set 72
V +106/20/23, 14:28 -
core-ci voted on patch set 72 V +1 06/20/23, 14:35 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/42832
-
Nikita Hovratov uploaded patch set 73
V +106/20/23, 17:03 -
core-ci voted on patch set 73 V +1 06/20/23, 17:12 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/42837
-
Nikita Hovratov uploaded patch set 74
V +106/22/23, 08:19 -
core-ci voted on patch set 74 V -1 06/22/23, 08:30 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/42900
-
Nikita Hovratov uploaded patch set 75
V -106/22/23, 09:14 -
Nikita Hovratov uploaded patch set 76 06/22/23, 09:17
-
core-ci voted on patch set 76 V -1 06/22/23, 09:22 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/42905
-
core-ci voted on patch set 75 V +1 06/22/23, 09:23 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/42903
-
Nikita Hovratov rebased onto patch set 77
V -106/22/23, 09:32 -
core-ci voted on patch set 77 V -1 06/22/23, 09:34 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/42906
-
Nikita Hovratov uploaded patch set 78
V -106/22/23, 09:35 -
core-ci voted on patch set 78 V +1 06/22/23, 09:43 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/42907
-
Nikita Hovratov uploaded patch set 79
V +107/11/23, 16:21 -
core-ci voted on patch set 79 V -1 07/11/23, 16:23 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/44054
-
Nikita Hovratov uploaded patch set 80
V -107/11/23, 16:29 -
core-ci voted on patch set 80 V +1 07/11/23, 16:36 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/44056
-
Nikita Hovratov uploaded patch set 81
V +107/12/23, 23:15 -
core-ci voted on patch set 81 V +1 07/12/23, 23:28 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/44100
-
Nikita Hovratov uploaded patch set 82
V +108/04/23, 13:25 -
core-ci voted on patch set 82 V -1 08/04/23, 13:39 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/45069
-
Nikita Hovratov uploaded patch set 83
V -108/04/23, 15:13 -
core-ci voted on patch set 83 V +1 08/04/23, 15:20 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/45077
-
Nikita Hovratov abandoned the change 02/18/24, 15:44
Outdated, new patch will be provided soon.
GeneralUtility.php:29