Review main Merged

91566[TASK] Add "debug:backend:modules", "debug:backend:routes" commands

Garvin Hicking CR +2 V +2 Hard +454 −0 updated 11/14/25, 06:15

Commit message

These CLI commands help developers to see:

- the list of registered backend modules and their hierarchy, along
  their extension origin and defined (translated) labels

- the list of backend routes and their targets

Two backend module list metadata items are not exposed through the
ModuleInterface API (and normally not relevant), so they are fetched
on a low-level basis.

With these command, developers are able to:

- debug the hierarchy and make choices about possible naming
  conflicts, ill-fated identifiers and proper ordering

- investigate AJAX routes, possible cross-concerns and scopes

Since this is regarded internal usage, it is not exposed
as a feature and uses a "debug:" CLI scope.

Review

  • Code review CR +2 Done
    • Georg Ringer +2
    • Sven Liebert +1
  • Verified V +2 Done
    • Georg Ringer +2
    • Sven Liebert +1
    • core-ci +1 CI

Issues 6

Files 3

Review log 1926

Show 1 earlier messages
  1. Garvin Hicking uploaded patch set 1 11/11/25, 18:01

  1. core-ci voted on patch set 1 V +1 11/11/25, 18:09 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/89048

  2. Garvin Hicking uploaded patch set 2 V +1 11/12/25, 16:26

  3. Garvin Hicking uploaded patch set 3 11/12/25, 16:27

  4. Garvin Hicking updated the commit message in patch set 4 11/12/25, 16:28

  5. core-ci voted on patch set 3 V -1 11/12/25, 16:38 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/89367

  6. core-ci voted on patch set 4 V -1 11/12/25, 16:39 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/89368

  7. core-ci voted on patch set 2 V -1 11/12/25, 17:05 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/89366

  8. Garvin Hicking uploaded patch set 5 V -1 11/12/25, 21:49

  9. core-ci voted on patch set 5 V +1 11/12/25, 21:57 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/89406

  10. Sven Liebert voted on patch set 5 CR +1 V +1 11/13/25, 16:46

  11. Lina Wolf voted on patch set 5 CR +1 V +1 11/13/25, 16:48

  12. Stefan Bürk commented on patch set 5 CR -1 11/13/25, 17:49

    * IMO is this a FEATURE -> prefix / restfile * command needs to be registered in Services.yaml as non-schedulable. * Not sure if it make sense at the current time (modules) - not into the module topic, if there will be changes or something else ....
  13. Garvin Hicking commented on patch set 5 11/13/25, 18:05

    Reply

    IMO no, because it's internal. I initially discussed this with @benni@typo3.org and we believe commands like these must not necessarily be exposed through a feature ReST file. Also because the commands have pretty self-explanatory usage and discovery through the CLI for the target audience. This would help a lot to actually DO the work on modules and see the output. Please have a look at the output of the tool and you'll see how helpful it can be. I'd be very happy if you could retract your negative vote to make the moves of navigation possible in the short time we have left for v14.0.
  14. Garvin Hicking commented on patch set 5 11/13/25, 18:06

    Reply

    Example where this would help a lot: https://review.typo3.org/c/Packages/TYPO3.CMS/+/91585
  15. Garvin Hicking commented on patch set 5 11/13/25, 18:16

    From Stefan, todo: - Register schedulable:false via Services.yaml for now - Mark classes "internal" - Add "for development purpose" to help text I'm not sure I'll have time for this though before next friday. If anyone wants to take a stab, please feel free to move forward, I'd appreciate that.
  16. Sven Liebert commented on patch set 5 CR 0 V 0 11/13/25, 18:31

    Reply

    On it
  17. Sven Liebert uploaded patch set 6 CR +1 V +1 11/13/25, 18:38

  18. Sven Liebert commented on patch set 6 CR +1 V +1 11/13/25, 18:39

    Reply

    Done

    Reply

    Solved with schedulable: false and marking as internal
  19. Georg Ringer commented on patch set 6 CR +1 V +1 11/13/25, 18:44

    I would drop the "for development purpose", as long as it is internal - we don't really care if the user develops something
  20. core-ci voted on patch set 6 V -1 11/13/25, 18:46 Core CI is not happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/89566

  21. Sven Liebert uploaded patch set 7 CR +1 V +1 11/13/25, 19:05

  22. Sven Liebert voted on patch set 7 CR +1 V +1 11/13/25, 19:08

  23. core-ci voted on patch set 7 V +1 11/13/25, 19:13 Core CI is happy: https://git.typo3.org/typo3/CI/cms/-/pipelines/89571

  24. Georg Ringer voted on patch set 7 CR +2 V +2 11/14/25, 06:15

  25. Georg Ringer merged patch set 8 11/14/25, 06:15