73119[TASK] Update PHP Parser to the latest release.
Commit message
Review
-
Code review CR +2 Done
- Christian Kuhn +2
- Oliver Hader +1
-
Verified V +2 Done
- Christian Kuhn +2
- Oliver Hader +1
- core-ci +1 CI
Issues 1
Files 4
Review log 2026
Show 1 earlier messages
-
crell uploaded patch set 1 01/21/22, 17:06
-
core-ci voted on patch set 1 V -1 01/21/22, 17:17 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/22364
-
crell uploaded patch set 2 01/21/22, 17:41
-
core-ci voted on patch set 2 V +1 01/21/22, 17:52 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/22365
-
Stefan Bürk updated the commit message in patch set 3 01/21/22, 17:59
-
Stefan Bürk updated the commit message in patch set 4 01/21/22, 17:59
-
crell voted on patch set 4 CR +1 01/21/22, 18:09
-
core-ci voted on patch set 3 V +1 01/21/22, 18:13 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/22366
-
core-ci voted on patch set 4 V +1 01/21/22, 18:15 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/22367
-
Oliver Klee voted on patch set 4 CR +1 01/21/22, 18:30
-
Christian Kuhn commented on patch set 4 01/21/22, 18:50
-
Stefan Bürk uploaded patch set 5 01/21/22, 18:57
-
Stefan Bürk commented on patch set 5 01/21/22, 19:00
composer.lock:8340ReplyMaybe because of used composer 2.1.x ? Pushed redo with composer 2.2.4 without having this change. Anyway, composer.json sais ^2.1 ... and this is the lock file, maybe it's just a info with which composer version last lockfile was updated, and not as a req check or something like that ? -
core-ci voted on patch set 5 V +1 01/21/22, 19:11 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/22369
-
Christian Kuhn commented on patch set 5 01/21/22, 19:26
composer.lock:8340Replyyeah, guess so, too. thx! -
Christian Kuhn commented on patch set 5 01/21/22, 19:27
btw: we should test if extension scanner is still happy (i think it has little to no ac test coverage, yet, only a bunch of unit tests for matchers). -
Benni Mack commented on patch set 5 01/22/22, 12:13
Should we also do this for 11.5 then? -
Oliver Klee voted on patch set 5 CR +1 01/22/22, 13:08
-
Stefan Bürk commented on patch set 5 01/22/22, 18:31
Reply
Think that's a valid point. Cannot do that until Sunday evening ....Reply
I would say, if we checked scanner like lollie mentioned, and it works we should check that for 11.5 to ... and raising this as backport too. Especially because this is not a dev dependency. What else does use this library in the core ? Only the scanner or something else ? Which 3rd party compomponents may use it ? -
Oliver Hader voted on patch set 5 CR +1 01/24/22, 08:21
-
Oliver Hader updated the commit message in patch set 6 01/24/22, 08:23
-
Oliver Hader commented on patch set 6 CR +1 01/24/22, 08:26
PHP Parser should be fine for the AST classes we use. On the resolving part, probably `NameResolver` should be verified concerning `namespacedName`.. -
core-ci voted on patch set 6 V +1 01/24/22, 08:38 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/22444
-
Oliver Hader commented on patch set 6 V +1 01/24/22, 09:38
No namespace-specific values of `NameResolver` are used in our code... -
Christian Kuhn voted on patch set 6 V +2 CR +2 01/24/22, 09:49
-
Christian Kuhn merged patch set 7 01/24/22, 09:49
composer.lock:8340