Review main Abandoned

89581[WIP][TASK] Allow "default" type as fallback in FormEngine / TCA

Benni Mack CR 0 V 0 Normal +140 −4 updated 05/04/26, 13:59

Commit message

When working with TCA and "types" key, historically
we had a "0" and "1" type, otherwise it wouldn't have
been rendered.

This makes sense for TCA where a type field is available
such as "be_users", or "pages". but for "tt_content", "0"
and "1" is very cryptic. Or for TCA where there is no
type, this is strange and very uncommon for newcomers.

This change adds "default" as well, which is currently
only evaluated in FormEngine anyways.

Review

  • Code review CR 0
  • Verified V 0
    • core-ci +1 CI

Files 2

Review log 912

  1. Benni Mack uploaded patch set 1 05/28/25, 09:37

  2. core-ci voted on patch set 1 V +1 05/28/25, 09:45 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/79626

  3. Oli Bartsch commented on patch set 1 CR -2 05/28/25, 10:17

    Unresolved

    Please wait. Migrating to Schema, I think we don't need this anymore at all.
  4. Benni Mack marked it work in progress 06/02/25, 10:46

  5. Oli Bartsch commented on patch set 1 09/02/25, 16:20

    DatabaseRecordTypeValue.php:146 Unresolved

    We would need to check "BackendUtility::getTCAtypeValue()" and `DatabaseRowInitializeNew->getRecordTypeFromRow` which use the same code.
  6. Oli Bartsch commented on patch set 1 CR 0 09/23/25, 13:47

    This change is ready for review.
  7. Oli Bartsch uploaded patch set 2 V +1 09/23/25, 15:26

  8. core-ci voted on patch set 2 V +1 09/23/25, 15:36 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/85397

  9. Oli Bartsch rebased onto patch set 3 V +1 10/20/25, 08:22

  10. core-ci voted on patch set 3 V +1 10/20/25, 08:49 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/87059

  11. Benni Mack marked it work in progress 01/25/26, 11:39

  12. Benni Mack abandoned the change 05/04/26, 13:59

    won't do, seems like we only have little interest in doing this now.