We have another use case which would require a language specific configuration, but not related to translations.
For our product, we require to have an account on our backend for each language. So every sales channel and language combination needs different account IDs and different API keys within the plugin configuration.
To make it possible in the current state, we needed to implement a different config handling with an additional database table including a "language_id" column. It also required us to implement a customized config page.
We have another use case which would require a language specific configuration, but not related to translations.
For our product, we require to have an account on our backend for each language. So every sales channel and language combination needs different account IDs and different API keys within the plugin configuration.
To make it possible in the current state, we needed to implement a different config handling with an additional database table including a "language_id" column. It also required us to implement a customized config page.