Repository navigation
[FEATURE] Support coalesce/concat resolution strategies for synchronizeColumns - #376
Merged
sfroemkenjw merged 1 commit intoAug 19, 2026
Conversation
…zeColumns Backport of the foreignColumnName coalesce/concat resolution feature from main (#375) to TYPO3 13. foreignColumnName previously only accepted a single, hard-coded column name, which made it impossible to synchronize a value that may live in one of several columns (e.g. company vs. name) or that has to be combined from multiple columns (e.g. first_name + last_name). The new ForeignColumn value object resolves foreignColumnName as a composite: a plain string still works as before, while an array with type coalesce/concat (or a bare list, treated as an implicit coalesce) can combine and nest arbitrarily. The static Maps2Registry::getInstance()->add() registration API and its JSON-backed registry are intentionally kept as-is; only the interpretation of the `synchronizeColumns[].foreignColumnName` option changed. The TcaSchemaFactory-based registry rewrite and TCA-embedded registration from main's TYPO3 14 line are out of scope for this branch. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
sfroemkenjw
deleted the
backport-synchronizeColumns-coalesce-concat-13-4
branch
August 19, 2026 13:17
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
foreignColumnNamecoalesce/concat resolution feature forsynchronizeColumnsfrommain(Support coalesce/concat resolution strategies for synchronizeColumns #375) to TYPO3 13.foreignColumnNamepreviously only accepted a single, hard-coded column name of the foreign table. It can now also be a coalesce (first non-empty value wins) or concat (join multiple columns) configuration, arbitrarily nestable.Maps2Registry::getInstance()->add()registration API and its JSON-backed registry are intentionally not touched — only the interpretation of thesynchronizeColumns[].foreignColumnNameoption changed. TheTcaSchemaFactory/TCA-embedded registration rewrite that ships onmainfor TYPO3 14 is out of scope here.Test plan
Build/Scripts/runTests.sh -s unit— 46/46 green, incl. 28 newForeignColumnTestcasesBuild/Scripts/runTests.sh -s functional(SQLite) — 287/287 green, no new failures/deprecations vs. baseline (286/1 deprecation)Build/Scripts/runTests.sh -s cgl -n) — 0 violations🤖 Generated with Claude Code