Bug #97295
closedTYPO3 core package replaces Symfony polyfills
100%
Description
While Symfony documents, that those polyfills could be replaced https://github.com/symfony/polyfill/#design
it does not mean that libraries should do so. In fact, even when documented by Symfony, adding a replace to a package, that in fact does not replace the functionality works, but is semantically still wrong.
This "hack" is quite acceptable for a concrete project, but should not be applied for libraries.
It is enough to declare PHP version constraints and leave it to concrete projects to add these replaces (or not).
As such: It would be fine to keep them for typo3/cms, but they should be removed from typo3/cms-core
Updated by Gerrit Code Review over 2 years ago
- Status changed from New to Under Review
Patch set 1 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/74169
Updated by Gerrit Code Review over 2 years ago
Patch set 2 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/74169
Updated by Gerrit Code Review over 2 years ago
Patch set 3 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/74169
Updated by Christian Kuhn over 2 years ago
- Related to Task #96980: Replace most symfony/polyfill-* packages added
Updated by Gerrit Code Review over 2 years ago
Patch set 4 for branch main of project Packages/TYPO3.CMS has been pushed to the review server.
It is available at https://review.typo3.org/c/Packages/TYPO3.CMS/+/74169
Updated by Helmut Hummel over 2 years ago
- Status changed from Under Review to Resolved
- % Done changed from 0 to 100
Applied in changeset 824f5e7db354e4ee99b1f188e4f5c439a6fa5315.