[AB-73] adding different feature modes to define whether or not certain actions should be logged, changing name of setup, disable and enable command to show that they are supposed to be for features

This commit is contained in:
Sheldan
2020-10-17 16:26:02 +02:00
parent 44dfdca6e6
commit 1b98436736
53 changed files with 525 additions and 165 deletions

View File

@@ -14,7 +14,7 @@ public class InvalidCategoryException extends AbstractoRunTimeException implemen
@Override
public String getTemplateName() {
return "setup_category_not_valid_exception";
return "feature_setup_category_not_valid_exception";
}
@Override

View File

@@ -23,7 +23,7 @@ public class ModMailCategoryDelayedActionConfig implements DelayedActionConfig {
@Override
public String getTemplateName() {
return "setup_modmail_category_action";
return "feature_setup_modmail_category_action";
}
@Override

View File

@@ -73,7 +73,7 @@ public class ModMailCategorySetupBean implements ModMailCategorySetup {
*/
@Override
public CompletableFuture<SetupStepResult> execute(AServerChannelUserId user, SetupStepParameter parameter) {
String messageTemplateKey = "setup_modmail_category_message";
String messageTemplateKey = "feature_setup_modmail_category_message";
SetupModMailCategoryMessageModel model = SetupModMailCategoryMessageModel
.builder()
.build();