Skip to content

Conversation

@Starkmann
Copy link
Contributor

@Starkmann Starkmann commented Feb 2, 2026

Part of #1332

@coveralls
Copy link

coveralls commented Feb 2, 2026

Pull Request Test Coverage Report for Build 21597349897

Details

  • 0 of 0 changed or added relevant lines in 0 files are covered.
  • No unchanged relevant lines lost coverage.
  • Overall coverage remained the same at 100.0%

Totals Coverage Status
Change from base Build 21596589551: 0.0%
Covered Lines: 111
Relevant Lines: 111

💛 - Coveralls

@oliverklee oliverklee force-pushed the task/1332-make-plugin-ctype-without-wizard branch from cdebf22 to 45941cd Compare February 2, 2026 15:58
@oliverklee oliverklee changed the title Task/1332 make plugin ctype without wizard [TASK] Make the plugin a CType Feb 2, 2026
@oliverklee oliverklee moved this to In review in Best Practices Remote Day Feb 2, 2026
@oliverklee oliverklee requested a review from a team February 2, 2026 15:59

excludePaths:
# We need this Class only for V12. So we exclude it here
- ../../Classes/Upgrades/AbstractListTypeToCTypeUpdate.php
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is related to the upgrade wizard (which is not part of this PR). So we don't need the changed to this file in this PR.

->autowire()
->autoconfigure();
->autoconfigure()
->public();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this needed for this PR? If so, why?

/**
* Register TeaIndex as "Insert Record"
*/
ExtensionManagementUtility::addToInsertRecords('tea_index');
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If we do this, we should have the other plugins as well.

);
foreach ($plugins as $contentType) {
// This makes the plugin selectable in the BE.
ExtensionUtility::registerPlugin(
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ExtensionUtility::registerPlugin returns the plugin signature. Can we (re-)use it for ExtensionManagementUtility::addToAllTCAtypes and ExtensionManagementUtility::addPiFlexFormValue?

<target>Teeliste</target>
</trans-unit>
<trans-unit id="plugin.tea_index.description">
<source>Tea plugin to show the listview.</source>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
<source>Tea plugin to show the listview.</source>
<source>Tea plugin to show the list view.</source>

(also in the other file)

,1,1,"list","Tea index","tea_teaindex","<?xml version=""1.0"" encoding=""utf-8"" standalone=""yes"" ?>
,"uid","pid","CType","header","pi_flexform"
,1,1,"tea_teaindex","Tea index","<?xml version=""1.0"" encoding=""utf-8"" standalone=""yes"" ?>
<T3FlexForms>
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should indent the XML to align with the <?xml again.

"psr/http-message": "^1.0.1",
"typo3/cms-core": "^12.4.41",
"typo3/cms-extbase": "^12.4.41 || ^13.4",
"typo3/cms-fluid": "^12.4.41 || ^13.4",
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, this needs to stay as we have Fluid templates.

ExtensionUtility::PLUGIN_TYPE_CONTENT_ELEMENT
);

ExtensionManagementUtility::addPageTSConfig('@import \'EXT:tea/Configuration/TSconfig/Page/ContentElementWizard.tsconfig\'');
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This file does not exist, and this PR does not introduce it. So this line should be removed.

@oliverklee oliverklee moved this from In review to In Progress in Best Practices Remote Day Feb 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: In Progress

Development

Successfully merging this pull request may close these issues.

4 participants