Review main Merged Breaking

90268[!!!][TASK] Drop support for Extbase Annotations

Elias Häußler CR +2 V +2 Expert +444 −669 updated 10/17/25, 08:23

Commit message

This patch drops support for all annotations in Extbase.

Existing annotations should be replaced by their appropriate
representation as PHP Attributes, which is already possible since
TYPO3 v12. This affects models/DTOs as well as controllers.

Example migration
=================

Before:
-------

    use TYPO3\CMS\Extbase\Annotation as Extbase;
    use TYPO3\CMS\Extbase\DomainObject\AbstractEntity;

    class MyModel extends AbstractEntity
    {
        /**
         * @Extbase\Validate("NotEmpty")
         */
        protected string $foo = '';
    }

After:
------

     use TYPO3\CMS\Extbase\Attribute\Validate;
     use TYPO3\CMS\Extbase\DomainObject\AbstractEntity;

     class MyModel extends AbstractEntity
     {
         #[Validate(['validator' => 'NotEmpty'])]
         protected string $foo = '';
     }

With this change, doctrine/annotations can be removed as well.

Used commands:

     composer remove doctrine/annotations && \
     composer remove \
       -d typo3/sysext/core --no-update --no-install \
       doctrine/annotations && \
     Build/Scripts/runTests.sh -s phpstanGenerateBaseline

Review

  • Code review CR +2 Done
    • Garvin Hicking +2
    • Torben Hansen +1
    • Simon Schaufelberger +1
  • Verified V +2 Done
    • Garvin Hicking +2
    • Oliver Klee +1
    • Torben Hansen +1
    • Simon Schaufelberger +1
    • core-ci +1 CI

Issues 1

Files 62

Show 42 more files

Review log 7496

Show 5271 earlier messages
  1. Elias Häußler uploaded patch set 1 08/07/25, 19:23

  2. Elias Häußler uploaded patch set 2 08/07/25, 19:37

  3. core-ci voted on patch set 1 V -1 08/07/25, 19:37 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/82882

  4. core-ci voted on patch set 2 V -1 08/07/25, 20:01 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/82887

  5. Elias Häußler uploaded patch set 3 V -1 08/07/25, 20:43

  6. core-ci voted on patch set 3 V -1 08/07/25, 21:23 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/82928

  7. Elias Häußler uploaded patch set 4 V -1 08/07/25, 21:29

  8. core-ci voted on patch set 4 V -1 08/07/25, 21:43 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/82941

  9. Elias Häußler uploaded patch set 5 V -1 08/07/25, 22:02

  10. core-ci voted on patch set 5 V +1 08/07/25, 22:18 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/82958

  11. Elias Häußler uploaded patch set 6 V +1 08/08/25, 11:58

  12. core-ci voted on patch set 6 V +1 08/08/25, 12:05 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/83012

  13. Elias Häußler uploaded patch set 7 V +1 08/08/25, 12:06

  14. Elias Häußler marked it ready for review 08/08/25, 12:08

  15. core-ci voted on patch set 7 V +1 08/08/25, 12:13 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/83013

  16. Simon Schaufelberger voted on patch set 7 CR +1 08/08/25, 12:20

  17. Markus Klein commented on patch set 7 08/08/25, 13:52

    FileUpload.php:31

    Was this without any effect? Is there any replacement now?
  18. René Pflamm voted on patch set 7 CR +1 08/08/25, 14:28

  19. Elias Häußler commented on patch set 7 08/08/25, 14:47

    FileUpload.php:31 Reply

    In this patch, there is now effective replacement. However, I created https://review.typo3.org/c/Packages/TYPO3.CMS/+/90296 which aims to fill this gap by introducing required properties for attributes (which replace the currently used array as parameter in the attribute constructors).
  20. Stefan Bürk commented on patch set 7 08/11/25, 00:04

    @elias@haeussler.dev We usually add the used (composer) commands to the commit message as a `Used command(s)` block like for example here https://review.typo3.org/c/Packages/TYPO3.CMS/+/88596 Example: ``` BIN_COMPOSER="$( which composer )" \ && ${BIN_COMPOSER} require \ -d typo3/sysext/core --no-update --no-install \ 'doctrine/dbal':'>= 4.3.1 < 4.4.0' \ && ${BIN_COMPOSER} require \ -d typo3/sysext/install --no-update --no-install \ 'doctrine/dbal':'>= 4.3.1 < 4.4.0' \ && ${BIN_COMPOSER} require \ -d typo3/sysext/redirects --no-update --no-install \ 'doctrine/dbal':'>= 4.3.1 < 4.4.0' \ && ${BIN_COMPOSER} require -w \ 'doctrine/dbal':'>= 4.3.1 < 4.4.0' \ && Build/Scripts/runTests.sh -s phpstanGenerateBaseline ```

    FileUpload.php:31 Reply

    Not tested, but I guess that we could use the required attribute as replacement. See: https://github.com/symfony/symfony/issues/48909 ``` - /** - @required - / + #[\Symfony\Contracts\Service\Attribute\Required] ``` However, not sure if that works for customphp attributes anyway (or if that worked before).
  21. Stefan Bürk commented on patch set 7 08/11/25, 00:07

    And as an additional `@todo`, the `Build/Scripts/phpIntegrityChecks/AnnotationChecker.php` should be checked for annoation not valid anymore to mitigate adding non-working annoations in the future.
  22. Markus Klein commented on patch set 7 08/11/25, 07:04

    FileUpload.php:31 Reply

    So we should wait with this one until the replacements are in place. I'm not a big fan of removing stuff because the replacement is there soon™. We had that in the past.
  23. Elias Häußler uploaded patch set 8 CR +1 V +1 08/12/25, 13:33

  24. Elias Häußler commented on patch set 8 08/12/25, 13:34

    Reply

    Done

    Reply

    Done

    FileUpload.php:31 Reply

    The `@Required` annotation was previously parsed by Doctrine to indicate that a specific property was required (see https://github.com/doctrine/annotations/blob/v1.8.0/lib/Doctrine/Common/Annotations/DocParser.php#L545 for the implementation). Hence, I'd say that replacing it with a Symfony attribute does not have an effect on attribute parsing/validation. The "problem" with the follow-up patch I linked before is that it does not work in combination with Doctrine attributes (better said: It *does* work, but would be highly breaking). Ideally, we'd put both changes into one, but I fear that this would be too much changes in one patch.
  25. core-ci voted on patch set 8 V +1 08/12/25, 13:44 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/83204

  26. Stefan Froemken commented on patch set 8 CR -1 08/13/25, 07:58

    Doctrine Annotations are "Attribute", "Enum", "Required" and "Target" and I have never seen these real Doctrine annotations in any extbase extension

    Breaking-107229-RemovedSupportOfDoctrineAnnotationsInExtbase.rst:14

    I don't understand that. Which doctrine annotations? There are no Doctrine Annotations in Extbase.

    Breaking-107229-RemovedSupportOfDoctrineAnnotationsInExtbase.rst:42

    In your example below you use "Validate". That is a PHP Attribute, but that's not a "native" PHP attribute. This is a specific Extbase class which is marked as PHP attribute.

    Breaking-107229-RemovedSupportOfDoctrineAnnotationsInExtbase.rst:53

    As you see, it's an extbase annotation. The desired class is part of the extbase framework. The only relation to doctrine is the folder name "ORM". In these classes nothing relates to doctrine.

    Breaking-107229-RemovedSupportOfDoctrineAnnotationsInExtbase.rst:72

    Correct: From "extbase" and not "Doctrine"
  27. Alexander Schnitzler commented on patch set 8 08/14/25, 10:46

    Breaking-107229-RemovedSupportOfDoctrineAnnotationsInExtbase.rst:14 Reply

    It's about removing support for doctrine annotations in favor of attributes and get rid of the doctrine/annotations package. Currently both is still possible. To use the class as attribute and as annotation i.e. inside a phpdoc comment. The latter will no longer be possible with this change. It's not about annotations of the doctrine/anotations package, it's about marking functionality with an annoation instead of an attribute.

    Breaking-107229-RemovedSupportOfDoctrineAnnotationsInExtbase.rst:42 Reply

    @Annotation is what makes this class and the others an annotation.

    Breaking-107229-RemovedSupportOfDoctrineAnnotationsInExtbase.rst:53 Reply

    It's not about doctrine/orm, it's about doctrine/annotations. I guess it's best to check the ClassSchema class and see that we currently check for doctrine annotations and attributes.

    Breaking-107229-RemovedSupportOfDoctrineAnnotationsInExtbase.rst:72 Reply

    The classes, which have been created as annotations and which are currently both annotations and attributes at the same time are moved into the attributes namespace.
  28. Elias Häußler commented on patch set 8 08/14/25, 14:04

    Reply

    Technically, that's correct, yes. I was referring to Doctrine annotations as the annotations which are used in Extbase and parsed by Doctrine's `AnnotationReader`, hence the naming. But I'm of course open for a better naming here, especially if the one I used leads to confusion. What is removed by this patch is the possibility to have annotations in place (it actually doesn't matter if it's Extbase annotations or third-party annotations). PHP attributes should be used instead, and support for parsing annotations (by Doctrine's `AnnotationReader`) is dropped.

    Breaking-107229-RemovedSupportOfDoctrineAnnotationsInExtbase.rst:14 Reply

    Exactly what @git@alexanderschnitzler.de said (see my comment at patch level as well).

    Breaking-107229-RemovedSupportOfDoctrineAnnotationsInExtbase.rst:42 Reply

    Do you have suggestions for a better explanation? Or is your comment just about dropping the "native" part?

    Breaking-107229-RemovedSupportOfDoctrineAnnotationsInExtbase.rst:53 Reply

    Correct, thanks @git@alexanderschnitzler.de. Please check my comment at patch level regarding the naming of "Doctrine annotations".

    Breaking-107229-RemovedSupportOfDoctrineAnnotationsInExtbase.rst:72 Reply

    I don't understand your comment, @froemken@gmail.com. The FQCN of the attribute classes (which were also annotations before) was moved from `TYPO3\CMS\Extbase\Annotation` to `TYPO3\CMS\Extbase\Attribute`. There's no Doctrine involved here.
  29. Elias Häußler uploaded patch set 9 CR -1 V +1 08/14/25, 14:41

  30. core-ci voted on patch set 9 V +1 08/14/25, 14:49 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/83394

  31. Benni Mack uploaded patch set 10 V +1 08/14/25, 15:54

  32. core-ci voted on patch set 10 V +1 08/14/25, 16:02 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/83403

  33. Stefan Froemken commented on patch set 10 08/14/25, 18:48

    Thank you for clarifying my remarks in new patch.

    Backend.php:311

    Should be "the". You add a very specific attribute here.
  34. Stefan Froemken commented on patch set 11 V +1 08/14/25, 19:21

    Published edit on patch set 10.
  35. Stefan Froemken commented on patch set 11 CR +1 08/14/25, 19:21

    Backend.php:311 Reply

    Done
  36. core-ci voted on patch set 11 V +1 08/14/25, 19:31 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/83406

  37. Simon Schaufelberger commented on patch set 11 08/17/25, 06:35

    must be /** in order to be a proper doctype
  38. Elias Häußler uploaded patch set 12 CR +1 V +1 08/17/25, 14:24

  39. Elias Häußler commented on patch set 12 08/17/25, 14:25

    Reply

    Done
  40. Elias Häußler commented on patch set 12 08/17/25, 14:26

    Breaking-107229-RemovedSupportOfDoctrineAnnotationsInExtbase.rst:14 Reply

    Done

    Breaking-107229-RemovedSupportOfDoctrineAnnotationsInExtbase.rst:42 Reply

    Done

    Breaking-107229-RemovedSupportOfDoctrineAnnotationsInExtbase.rst:53 Reply

    Done

    Breaking-107229-RemovedSupportOfDoctrineAnnotationsInExtbase.rst:72 Reply

    Done
  41. core-ci voted on patch set 12 V +1 08/17/25, 14:32 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/83533

  42. Sascha Nowak voted on patch set 12 CR +1 08/18/25, 14:58

  43. Elias Häußler wrote 08/21/25, 06:55

    Topic set to extbase
  44. Elias Häußler uploaded patch set 13 CR +1 V +1 08/25/25, 12:58

  45. core-ci voted on patch set 13 V +1 08/25/25, 13:06 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/83846

  46. Benni Mack uploaded patch set 14 V +1 09/01/25, 15:22

  47. core-ci voted on patch set 14 V +1 09/01/25, 15:38 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/84175

  48. Garvin Hicking uploaded patch set 15 V +1 09/24/25, 21:59

  49. Garvin Hicking commented on patch set 15 CR +1 09/24/25, 22:01

    Generally this works and we should try to have this in v14 IMO. Some minor RST comments and I believe the class-aliasing doesn't fully work for the PropertyMapper?!

    Breaking-107229-RemovedSupportOfAnnotationsInExtbase.rst:93

    How about adding a note like: ``` .. hint:: Doing a "search and replace" can ideally be done programmatically with something like a Rector rule or similar. ``` Maybe @simonschaufi+typo3@gmail.com would chime in if it's likely that TYPO3 Rector will receive this for a v14 release and we can adjust the changelog later to refer to that rule...?

    Breaking-107229-RemovedSupportOfAnnotationsInExtbase.rst:103

    How about adding `TYPO3\CMS\Extbase\Annotation` to `typo3/sysext/install/Configuration/ExtensionScanner/Php/ClassNameMatcher.php` so that the Extension scanner will alert at both this migration and possible need to replace an annotation with an attribute?

    FileUpload.php:31 Reply

    Since this is the only place of the core that '@Required' is used, how about modifying the constructor to check for a non-empty 'validation' array and throwing a specific exception? The follow-up patch is IMO indeed too complex to merge it with this one. And I think it should not block/stalemate this current approach.

    ClassAliasMap.php:5

    This does not seem to work in practice for me. A model like this: ``` <?php declare(strict_types=1); namespace Garvinhicking\ExtbaseUpload\Domain\Model; use TYPO3\CMS\Extbase\Annotation\FileUpload; use TYPO3\CMS\Extbase\Domain\Model\FileReference; use TYPO3\CMS\Extbase\DomainObject\AbstractEntity; class Singlefile extends AbstractEntity { #[FileUpload([ 'validation' => [ 'maxFiles' => 1, ], 'uploadFolder' => '1:/user_upload/', ])] protected ?FileReference $fileUnrestrictedSingle = null; public function getFileUnrestrictedSingle(): ?FileReference { return $this->fileUnrestrictedSingle; } public function setFileUnrestrictedSingle(?FileReference $fileUnrestrictedSingle): void { $this->fileUnrestrictedSingle = $fileUnrestrictedSingle; } } ``` upon persisting in Extbase throws an: ``` (1/2) #1297759968 TYPO3\CMS\Extbase\Property\Exception Exception while property mapping at property path "fileUnrestrictedSingle": The source is not of type string, array, float, integer or boolean, but of type "object" in /var/www/html/typo3-core/typo3/sysext/extbase/Classes/Property/PropertyMapper.php line 66 ```
  50. core-ci voted on patch set 15 V +1 09/24/25, 22:06 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/85469

  51. Garvin Hicking uploaded patch set 16 CR +1 V +1 09/25/25, 08:33

  52. core-ci voted on patch set 16 V +1 09/25/25, 08:46 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/85491

  53. Garvin Hicking commented on patch set 16 09/25/25, 17:03

    ClassAliasMap.php:5 Reply

    I think this was missing to to the composer.json entries, Stefan Bürk hinted me at that. It works now with core classes, but for me not for locally fetched extensions. Might be specific to my monorepo-composer setup, so resolving this.
  54. Garvin Hicking uploaded patch set 17 V +1 09/25/25, 18:31

  55. Garvin Hicking commented on patch set 17 CR -1 09/25/25, 18:34

    ClassAliasMap.php:5 Reply

    I created a test that sadly seems to prove that the aliased namespace does in fact not seem to work properly. Changing line 20 `typo3/sysext/extbase/Tests/Functional/Fixtures/Extensions/test_validators/Classes/Domain/Model/AliasedModel.php` from `use TYPO3\CMS\Extbase\Annotation` to `use TYPO3\CMS\Extbase\Attribute` makes the test pass. Sadly I don't know enough of the gory details how aliasing should/could work. If it doesn't work I guess we would first have to deprecate the usage before we can remove it to have the 2-version LTS compatibility in place.
  56. core-ci voted on patch set 17 V -1 09/25/25, 18:41 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/85544

  57. Alexander Schnitzler commented on patch set 17 09/25/25, 19:15

    AliasedModel.php:20

    This is the wrong namespace. `Annotation` no longer exists. It's `Attribute`.

    AliasedModel.php:39

    Aliasing isn't a TYPO3 feature, it's plain PHP. Your IDE will show that the classes used here don't exist due to the wrong namespace.
  58. Garvin Hicking commented on patch set 17 09/25/25, 19:30

    AliasedModel.php:20 Reply

    But that's the idea of the Alias, isn't it? To allow using the "old" namespace as long as it's aliased? I thought this is a feature of the Class Loader, because composer also does things there. Also: This works when I insert the statement into a TYPO3 core controller (like in EXT:form's controller in the `renderAction`). I don't understand why it works there and not inside a testing-framework or custom composer package.
  59. Alexander Schnitzler commented on patch set 17 09/25/25, 20:00

    AliasedModel.php:20 Reply

    I am not sure how you define an alias here. I thought you mean the `Annotation as Extbase` or `Attribute as Extbase` alias. I don't know of any class loader specific aliasing. If that exists, I am not familiar with it and someone else needs to step in here. My unnderstanding of this patch is that Annotations classes are removed (breaking) and that people MUST switch from Annotation (classes) to Attribute (classes) as explained in the commit message. Maybe I am wrong here. Don't know atm.
  60. Andreas Kienast commented on patch set 17 09/26/25, 04:37

    ClassAliasMap.php:5 Reply

    Just to rule out the obvious one: did you run `composer dump-autoload`?

    AliasedModel.php:20 Reply

    > If that exists, I am not familiar with it and someone else needs to step in here. Please see the changes in EXT:extbase/composer.json and EXT:extbase/Migrations/Code/ClassAliasMap.php – this feature exists since TYPO3 v6.
  61. Alexander Schnitzler commented on patch set 17 09/26/25, 05:48

    ClassAliasMap.php:5 Reply

    I just did and it actually doesn't work despite having those entries in autoload_classaliasmap.php: `'typo3\\cms\\extbase\\annotation\\orm\\cascade' => 'TYPO3\\CMS\\Extbase\\Attribute\\ORM\\Cascade'` Can't rule out that it's my setup as well but I am quite sure it's not. I ran dumpautoload inside the core repo and I am running the functional tests from within there as well. It should reflect the behaviour of the CI job.

    AliasedModel.php:20 Reply

    Hehe, I am sorry. I slightly remember this now from the t3lib_div days but I was completely unaware this still exists. I just had a brief moment to check this patch and jumped to conclusions too quickly because I thought it's about the native aliasing feature of PHP.

    AliasedModel.php:39 Reply

    Done
  62. Andreas Kienast commented on patch set 17 09/26/25, 07:39

    ClassSchema.php:144

    These classes reference the new `\Attribute` namespace, which in turns leads to the situation that the old `\Annotation` namespace, as used in the `AliasedModel` test case, is ignored.
  63. Garvin Hicking commented on patch set 17 CR 0 09/26/25, 08:48

    ClassSchema.php:144 Reply

    Thanks for diving into this, I understand. So basically this means we cannot keep the old alias in place easily. If I see this correctly, we should only deprecate the old namespace (if I see correctly, this has not been done yet), keep the old namespace for now, and then do the breaking change in v15? This patch could still replace annotations with attributes, but in the old namespace, right?

    ClassAliasMap.php:5 Reply

    See Andis explanation below, resolving this thread.

    AliasedModel.php:20 Reply

    Thanks for jumping to help, it was (is) all a bit fuzzy to me. Resolving this one here. :)
  64. Elias Häußler commented on patch set 17 09/26/25, 09:22

    ClassSchema.php:144 Reply

    Thank you very much for these insights! This is indeed a problem.. Could it be solved like this? ``` \TYPO3\CMS\Extbase\Attribute\Validate::class, \TYPO3\CMS\Extbase\Annotation\Validate::class => $validateAttributes[] = $attribute, ``` We could then remove the second match (the one with `Annotation` namespace) with v15.
  65. Elias Häußler uploaded patch set 18 V -1 09/26/25, 09:38

  66. Elias Häußler commented on patch set 18 09/26/25, 09:39

    ClassSchema.php:144 Reply

    The failing test went green locally with this change, so I pushed it as new patchset. Please have a second look. 😊
  67. core-ci voted on patch set 18 V +1 09/26/25, 09:48 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/85587

  68. Andreas Kienast commented on patch set 18 CR -1 09/26/25, 11:13

    ClassSchema.php:144 Reply

    I'll push another support file for IDEs.
  69. Andreas Kienast uploaded patch set 19 CR -1 V +1 09/26/25, 11:15

  70. core-ci voted on patch set 19 V +1 09/26/25, 11:25 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/85592

  71. Garvin Hicking commented on patch set 19 CR +1 V +1 09/26/25, 23:29

    ClassSchema.php:144 Reply

    Done
  1. Oliver Klee voted on patch set 19 V +1 09/27/25, 13:54

  2. Simon Schaufelberger commented on patch set 19 09/30/25, 08:36

    Breaking-107229-RemovedSupportOfAnnotationsInExtbase.rst:93 Reply

    since my budget got approved, I'll try on create a rule for that when merged.
  3. Garvin Hicking commented on patch set 19 09/30/25, 11:00

    Breaking-107229-RemovedSupportOfAnnotationsInExtbase.rst:93 Reply

    Cool. I'll resolve this for now, I think we should then add this hint later, and then we could directly link to the rule.
  4. Garvin Hicking commented on patch set 19 09/30/25, 11:05

    FileUpload.php:31 Reply

    ... actually, the `FileUploadConfiguration` class that consumes this attribute already has this check in place: ``` if (!isset($configuration['validation']) || $configuration['validation'] === []) { throw new \RuntimeException('Extbase file upload must at least define one validation rule.', 1711947120); } ``` so this 'Required' use wouldn't fall flat, and is still enforced on code-level. I would like to resolve this, please re-open in case of complaints. 😊
  5. Elias Häußler uploaded patch set 20 CR +1 V +1 09/30/25, 17:55

  6. Elias Häußler commented on patch set 20 09/30/25, 17:56

    Breaking-107229-RemovedSupportOfAnnotationsInExtbase.rst:103 Reply

    Done
  7. Garvin Hicking commented on patch set 20 CR +1 V +1 09/30/25, 17:58

    Breaking-107229-RemovedSupportOfAnnotationsInExtbase.rst:103 Reply

    Thanks! :)
  8. core-ci voted on patch set 20 V +1 09/30/25, 18:02 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/85753

  9. Elias Häußler uploaded patch set 21 CR +1 V +1 09/30/25, 18:16

  10. core-ci voted on patch set 21 V +1 09/30/25, 18:22 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/85754

  11. Elias Häußler uploaded patch set 22 V +1 09/30/25, 18:27

  12. core-ci voted on patch set 22 V +1 09/30/25, 18:34 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/85755

  13. Oliver Klee voted on patch set 22 V +1 09/30/25, 18:43

  14. Garvin Hicking voted on patch set 22 CR +1 V +1 09/30/25, 18:45

  15. Simon Schaufelberger voted on patch set 22 CR +1 V +1 09/30/25, 18:48

  16. René Pflamm wrote 09/30/25, 19:07

    Removed reviewer René Pflamm.
  17. Torben Hansen voted on patch set 22 CR +1 V +1 10/01/25, 16:08

  18. Garvin Hicking voted on patch set 22 CR +2 V +2 10/01/25, 16:53

  19. Garvin Hicking merged patch set 23 10/01/25, 16:53

  20. Lina Wolf commented on patch set 23 10/05/25, 06:25

    What about using the `@var` annotation instead of types properties? has that also been removed?
  21. Garvin Hicking commented on patch set 23 10/05/25, 06:51

    Reply

    No, these are php-doc annotations, see changelog: "Note that usage of PHPDoc annotations like :php:`@param`, :php:`@return` and others are unaffected by this change, as they do not require specific Doctrine annotation parsing. Especially explicit parameter type annotations like :php:`@param ObjectStorage<MyModel>` are still fully supported."
  22. Lina Wolf commented on patch set 23 10/05/25, 11:38

    Reply

    I think, that the title of the changelog entry sounds quite misleading. Expecially since we have used the words annotation for these constructs no matter which syntax they used until now in the docs.
  23. Garvin Hicking commented on patch set 23 10/05/25, 13:19

    Reply

    Hm, I don't see it like this. we specifically mention extbase annotations and do differ them to php-doc annotations. php-doc annotations are just comments! extbase annotations are actively namespaced.
  24. Elias Häußler commented on patch set 23 10/06/25, 06:59

    Reply

    @112@linawolf.de @garvin@hick.ing I made a follow-up for the changelog file, please have a look at https://review.typo3.org/c/Packages/TYPO3.CMS/+/90907.
  25. Garvin Hicking commented on patch set 23 10/17/25, 08:23

    Reply

    Done