#107840Enhance language:domain:list command to support filtering and content search
Description
With changes like https://forge.typo3.org/issues/107810 language files will be renamed and moved.
So in my opinion it would be very helpful to be able to search for all language files for the key or text, possibly containing wildcards.
Add a —search <string> option to search for an exact string (case-insensitive) in label keys or default-language text.<br>Add a —regex <pattern> option to use regular expressions for flexible matching.<br>The existing —extension <name> option can be used together with these filters to limit results to a specific extension.</name></pattern></string>
These would be my scenarios:
bin/typo3 language:domain:list --search "Access"
core.general => EXT:core/Resources/Private/Language/locallang_general.xlf
- tabs.access => "Access"
frontend.tca => EXT:core/Resources/Private/Language/locallang_general.xlf
- pages.tabs.access => "Access"
- fe_users.tabs.access => "Access"
- sys_template.tabs.access => "Access"
...
bin/typo3 language:domain:list --search "tabs.access"
core.general => EXT:core/Resources/Private/Language/locallang_general.xlf
- tabs.access => "Access"
bin/typo3 language:domain:list --regex ".*access.*" -extension core
core.general => EXT:core/Resources/Private/Language/locallang_general.xlf
- tabs.access => "Access"
core.file_messages => EXT:core/Resources/Private/Language/locallang_general.xlf
- FileUtility.CouldNotAccessAllNecessaryResources => "Could not access all necessary resources. Source file or destination maybe was not within your mountpoints? T="%s", D="%s""
...
While experienced developers can use the power of their IDEs or consoles to search for such strings in the XLF files the same is much harder for integrators or new developers.
Reviews 2
Related issues 2
History 1322
-
Lina Wolf changed description <span data-processor="relativetime" data-value="2025-10-26T10:23:30+00:00" > 10/26/25, 10:23 </span>
-
Lina Wolf changed description <span data-processor="relativetime" data-value="2025-10-26T10:24:07+00:00" > 10/26/25, 10:24 </span>
-
Lina Wolf changed description <span data-processor="relativetime" data-value="2025-10-26T10:24:24+00:00" > 10/26/25, 10:24 </span>
-
Lina Wolf changed Related to #107839 <span data-processor="relativetime" data-value="2025-10-26T10:25:22+00:00" > 10/26/25, 10:25 </span>
-
Garvin Hicking commented and changed status
NewAccepted <span data-processor="relativetime" data-value="2025-10-26T11:52:16+00:00" > 10/26/25, 11:52 </span> -
Lina Wolf commented <span data-processor="relativetime" data-value="2025-10-26T14:26:48+00:00" > 10/26/25, 14:26 </span>
I think adding the searching and filtering directly would be more convenient to use. the JSON output is more a format when you want to communicate with an external service or some such
-
Garvin Hicking changed Duplicates #107845 <span data-processor="relativetime" data-value="2025-10-26T17:17:25+00:00" > 10/26/25, 17:17 </span>
-
Lina Wolf commented <span data-processor="relativetime" data-value="2025-10-27T13:04:41+00:00" > 10/27/25, 13:04 </span>
I just spoke with Benny and he suggested a separate command just to search for labels. Additional functionallity might be added in the future
-
Lina Wolf changed assigned to Lina Wolf <span data-processor="relativetime" data-value="2025-11-13T12:48:32+00:00" > 11/13/25, 12:48 </span>
-
Gerrit Code Review pushed patch set 1 for main to change 91614 status
AcceptedUnder Review <span data-processor="relativetime" data-value="2025-11-13T12:58:49+00:00" > 11/13/25, 12:58 </span> -
Gerrit Code Review pushed patch set 2 for main to change 91614 <span data-processor="relativetime" data-value="2025-11-13T12:59:27+00:00" > 11/13/25, 12:59 </span>
-
Gerrit Code Review pushed patch set 3 for main to change 91614 <span data-processor="relativetime" data-value="2025-11-13T13:00:07+00:00" > 11/13/25, 13:00 </span>
-
Gerrit Code Review pushed patch set 4 for main to change 91614 <span data-processor="relativetime" data-value="2025-11-13T13:41:24+00:00" > 11/13/25, 13:41 </span>
-
Gerrit Code Review pushed patch set 5 for main to change 91614 <span data-processor="relativetime" data-value="2025-11-13T14:27:39+00:00" > 11/13/25, 14:27 </span>
-
Gerrit Code Review pushed patch set 6 for main to change 91614 <span data-processor="relativetime" data-value="2025-11-13T15:01:46+00:00" > 11/13/25, 15:01 </span>
-
Gerrit Code Review pushed patch set 7 for main to change 91614 <span data-processor="relativetime" data-value="2025-11-13T21:15:16+00:00" > 11/13/25, 21:15 </span>
-
Lina Wolf changed parent task #108143 <span data-processor="relativetime" data-value="2025-11-16T05:46:29+00:00" > 11/16/25, 05:46 </span>
-
Gerrit Code Review pushed patch set 8 for main to change 91614 <span data-processor="relativetime" data-value="2025-11-18T17:48:20+00:00" > 11/18/25, 17:48 </span>
-
Gerrit Code Review pushed patch set 9 for main to change 91614 <span data-processor="relativetime" data-value="2025-11-18T17:49:07+00:00" > 11/18/25, 17:49 </span>
-
Lina Wolf commented and changed status
Under ReviewResolved done0 %100 % <span data-processor="relativetime" data-value="2025-11-18T18:15:08+00:00" > 11/18/25, 18:15 </span>Applied in changeset commit:4b459b3ca2a145772db6952eac0805a3486eed31.
-
Benni Mack changed status
ResolvedClosed <span data-processor="relativetime" data-value="2025-12-02T12:04:51+00:00" > 12/02/25, 12:04 </span> -
Garvin Hicking changed Related to #108743 <span data-processor="relativetime" data-value="2026-01-23T11:02:55+00:00" > 01/23/26, 11:02 </span>
I was planning to add a “json” output there, that could hold all contents (and be translation specific).
Such a json could then be filtered and grepped for. What do you think? I believe adding the searching/filtering directly in the command could still be helpful though.
I can offer to work on this.