Refactor some of the current Backend template flags to provide a more concise representation of their usage and include some extra flags to allow more granular control over the projects generated within the solution.
Context
Some of the current Backend template flags are useful but their naming and usage may lead to some confusions and misunderstandings, so it will be helpful to refactor them a bit to provide a more concise representation of their usage. Also, it's a good opportunity to include some extra flags to provide more switches over certain projects within the solution.
Detailed Description
Refactor some of the current Backend template flags to provide a more concise representation of their usage and include some extra flags to allow more granular control over the projects generated within the solution.
Context
Some of the current Backend template flags are useful but their naming and usage may lead to some confusions and misunderstandings, so it will be helpful to refactor them a bit to provide a more concise representation of their usage. Also, it's a good opportunity to include some extra flags to provide more switches over certain projects within the solution.
Possible Implementation
Each of them can be refactored as follows:
excludeCommon
commonLibraries
true
excludeFilesSupport
filesSupport
true
massTransitIntegration
apiGateway
disableAuth
auth
true
workerService
keycloakConfig
keycloakRealm
apiService
true
tests
true