Documentation

Code of Conduct

Service naming

We have several service types, so we want to reflect these types in the file name. It will allow us to easily determine the purpose of usage.

Default service (general-purpose, application business logic): *Service
Examples: LocalisationService, NavigationTreeService

Resource service (state management): *Resource
Examples: UserInfoResource, ConnectionInfoResource

Bootstrap service (application initiation logic): *Bootstrap
Examples: CustomConnectionMenuBootstrap, SQLEditorBootstrap