Question: Translationplugin loading order

[gvisbeen]

In laravel the language files are loaded before the route files, making using the translation files possible in the route paths. Trying the same with the route files in modules revealed that when loading the routes the module language files had not been loaded yet, resulting in unknown routes. I've written a workaround preloading all the translation files named route.php from every module and merging them. It would make more sense if changing the loading order was possible. Is there a solution that lets you do this?

[gvisbeen]

The class should be initialized directly after the Translator class has been resolved.

#[AfterResolving(Translator::class, parameter: 'translator')]

Placing echo statements in the route files and the plugin reveals that the routes are resolved before the plugin loads but after the Laravel Translater class is available.

I've solved it for now with a really ugly hack using a global in an global function:

$langPreload = true;
function langPreload() {
    global $langPreload;
    if($langPreload === true) {
        $ff = app(FinderFactory::class);
        $tp = app(TranslatorPlugin::class);
        $tc = collect($tp->discover($ff));
        try {
            $tp->handle($tc);
        } catch (Exception $e) {
        }
    }
}

and placing a call to the function langPreload() in the module route files. Cant see a proper way to resolve this other than creating a custom TranslationService and replacing the Laravel one so the plugin loading will be directly called after instead of an event.