(ui): default preferences value is set twice
Description
When using a preference key to set the value of a service configuration, you can set a default value in the preferences_configuration
service that exposes the preferences key, but in the meantime, you need to provide a default value when reading the key in case the preferences configuration has not been launched yet.
Of course, that poses the problem of the consistency of the default value. And who's first? One could "force" to update the preferences configuration services to create missing keys at start, but this would assume that the service is even started which might not the case if it contained in a pop-up window, a separate configuration, etc...
Functional specifications
Workflow, UX/UI design, screenshots, etc...
Technical specifications
Details of the implementation.
Test plan
Describe how you will verify that the implementation meets specifications.