> > this requires that any custom class is autoload-able or load it somehow else (auto-prepend .. though that is ugly).

> True, @patrickallaert some way to specify a required file maybe?
`auto_prepend_file` is more than adequate, it is rarely used and sometimes misused, but there is definitely nothing wrong with it.

We previously used a `config.php` file with some existence checks, but that's not as nice as using an existing feature. I would even say we somewhat reinvented the wheel previously in Legacy in this regard.

In any cases, something that this is definitely wanted is the **ability to register your very own autoloaders**. This PR might depend on that feature.

> Yes, this is one of the topic further up in the PR comments, our "problem" is that the Symfony approach causes issues for updates and upgrades (conflicts / wiped customizations / ..), so the idea behind this approach is to allow people to extend these files withouth changing them.

Can't agree more!

> @patrickallaert, @lsmith77, @lolautruche Something to discuss at the ezunconf in Montpellier maybe? (find a approach that could be contributed and accepted in symfony-standard)

Sure thing! :smile_cat: