Problem
The bundle exposes TranslatorDriverInterface, but normal configuration only accepts google as sfs_translatable.api.driver.
Current behavior
Applications cannot register and select a custom translation driver through the bundle configuration without extending internal loading logic.
Expected behavior
Applications should have a supported way to plug in another translation provider or internal service while keeping the API UI and controller flow.
Notes
At the moment the configuration enum and the api_driver/<driver>.yaml loading strategy make the extension point much narrower than the public interface suggests.
Problem
The bundle exposes
TranslatorDriverInterface, but normal configuration only acceptsgoogleassfs_translatable.api.driver.Current behavior
Applications cannot register and select a custom translation driver through the bundle configuration without extending internal loading logic.
Expected behavior
Applications should have a supported way to plug in another translation provider or internal service while keeping the API UI and controller flow.
Notes
At the moment the configuration enum and the
api_driver/<driver>.yamlloading strategy make the extension point much narrower than the public interface suggests.