[TASK] Replace TYPO3 localization override with EXT:deepl_base
#468
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.
EXT:deepltranslate_corereplaced TYPO3 backend implementationof the localization JavaScript modal to add two custom modes to
the system along with extending the
LocalizationControllertoensure processing works by mitigating the hardcoded core mode
checks implemented by the TYPO3 Core.
Meanwhile, a new planned extension also needs to provide one or
more custom modes, which should work standalone and or next to
EXT:deepltransate_corewhich makes providing hardcoded modeextension unreliable, special in a cross-mix.
To mitigate this a new
EXT:deepl_baseextension has been nowcreated to provide the overrides in a extensible way using the
one or other PSR-14 event, adding a new AJAX Endpoint for the
locaization modes and adjusts the JavaScript to be dynamically
changeable and is based on a early
work-in-progresschange forTYPO3 v14, provided as a early and slightly enhanced backport.
This change replaces the own implementation with the provided
events of the shared extension, dropping obsolete code directly
to keep it clean.
Current PSR-14 event based implementation lacks checking if
the
deepl api keyhas been set and will be added with oneof the following changes along with further adjustments.
This change acts as a kickstart for the replacement now to
open up for dual developlment on this extension and another
extension on the same time and unblock that.
However, it's still a working state and leads to the direction
already planned.
Used command(s):