You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
there are still inconsistencies in implementation patterns across various services. This discussion aims to discuss and unify these coding details to improve code consistency and maintainability.
Tasks
Implement Debug Trait for all service builders
Most service builders include corresponding service config fields. Special attention should be paid to whether sensitive information might be printed in the debug implementation.
Module and Structure Renaming
ServiceAccessor → ServiceBackend (to align the naming conventions of backend module)
delete module → deleter module (to align with naming conventions like writer, reader, lister)
Remove Empty list Operation Implementations
Only keep list implementations in services that actually provide this functionality
Remove useless list implementations from services that don't support this operation or have not implemented it yet.
Unify Scheme Usage
Prefer direct string-based scheme specification over enum-based approach
As discussed in #6752
Tasks
DebugTrait for all service buildersServiceAccessor→ServiceBackend(to align the naming conventions ofbackendmodule)deletemodule →deletermodule (to align with naming conventions likewriter,reader,lister)listOperation Implementationslistimplementations from services that don't support this operation or have not implemented it yet.SchemeUsageSchemeenum usage from bindingsSchemeenum