TYPO3 v13 Support - #34
Open
d-s-codappix wants to merge 8 commits into
Open
d-s-codappix wants to merge 8 commits into
d-s-codappix wants to merge 8 commits into
Conversation
d-s-codappix
force-pushed
the
feature/updateV13
branch
from
June 16, 2025 10:15
0e1a774 to
dcddb74
Compare
d-s-codappix
force-pushed
the
feature/updateV13
branch
5 times, most recently
from
September 18, 2025 13:16
094eba0 to
b348421
Compare
* Remove 12.4 support to not introduce fallbacks for deprecated API. * Use dependency injection. * Use new attributes to declare EventListener. * Adjust CI to new TYPO3 version.
To gain more comfort during upcoming upgrades, and this upgrade. To higher code quality.
As this is officially supported by TYPO3 v13.4
To prevent distribution of development only files.
d-s-codappix
force-pushed
the
feature/updateV13
branch
from
September 23, 2025 06:39
b348421 to
8fdbd5c
Compare
In order to ensure that the Extension works with TYPO3 version.
d-s-codappix
force-pushed
the
feature/updateV13
branch
from
September 23, 2025 06:43
8fdbd5c to
6a6e3ea
Compare
Author
|
This should be the final state. We still need to finish our TYPO3 update of the project, including manual testing with this extension. |
s12r
approved these changes
Sep 23, 2025
d-s-codappix
marked this pull request as draft
September 25, 2025 04:58
SomeBdyElse
marked this pull request as ready for review
January 23, 2026 11:12
This change raises the constraint to "php >= 8.2 < 8.6" and adds 8.5 to all three CI matrices (linting, tests, PHPStan). PHP 8.1 is dropped.
Markers whose key contains a slash were never replaced in the frontend output. The regular expression that searches for markers is built with a slash as delimiter, but the marker keys were escaped without telling the escaping function about that delimiter. A key such as "foo/bar" therefore ended the pattern early, and the resulting expression either failed or matched the wrong text. Editors saw the raw marker instead of its value. The marker keys are now escaped with the slash delimiter in mind, so every character of a key is treated as literal text. Markers containing slashes, dots or other characters with a special meaning in regular expressions are replaced like any other marker.
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
3 participants
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.
We already started with TYPO3 v13 adoption.
This is our current state. Feel free to build upon it.
This is marked as draft, as we aren't done yet.