TYPO3 Core

Joschi Kuphal wrote:

As a follow up to #67972, I'd vote for providing a reasonable way of flushing (or temporarily disabling) the autoloader cache other than manually clearing `typo3temp/autoload`. Just stating "it doesn't work anymore" seems as much of an option as "changing the extension list" after each creation of a new class during extension development. Including the autoloader cache into "clear system caches" (for example) would surely save quite some hours of helpless frustration.

Thank you for your report and suggestion.

The class loading information written to typo3temp/autoload however is no cache and thus should not be flushed with system caches.

To avoid frustration, you should add a composer.json to the extension you are developing and add a autoload/psr-4 section to it.
By doing so (and (re-)activating your extension in the extension manager, you can add as many psr-4 compliant classes as you like during development without the need to flush any class loading information at all.

Would you be fine if I'd close this ticket, once I added documentation for this fact in a prominent place?

What would be doable however, is a CLI command, which re-builds the autoload information (not flushing it).

If you think these steps are not enough, please explain the cases where you need more than that.

Closed; thank you for your feedback!