如何替换Java代码中的Switch Case实现？寻求优化方案

我有一段Java代码，功能是根据传入的字符串参数修改对应的静态常量，目前用Switch Case实现，想优化这段代码。试过用Map，但感觉和if语句没本质区别，没解决核心问题，求更优的实现方案。

现有代码如下：

public static void setMissingField(String missingField) {
    switch (missingField) {
        case "firstName":
            expectedFirstName = "";
            break;
        case "lastName":
            expectedLastname = "";
            expectedFirstName = "test";
            break;
        case "email":
            expectedWorkEmail = "";
            expectedLastname = "test";
            break;
        case "shortEmail":
            expectedWorkEmail = "12@yes";
            expectedLastname = "test";
            break;
        case "invalidEmail":
            expectedWorkEmail = "asb@@abc.com";
            expectedLastname = "test";
            break;
        case "company":
            expectedCompany = "";
            expectedWorkEmail = "abd@thank.you";
            break;
        case "password":
            expectedPassword = "";
            expectedCompany = "dontAsk";
            break;
        case "shortPassword":
            expectedPassword = "12Aa@";
            expectedCompany = "dontAsk";
            break;
        case "withoutLowerCasePassword":
            expectedPassword = "PASSWORD1@";
            expectedCompany = "dontAsk";
            break;
        case "withoutUpperCasePassword":
            expectedPassword = "password1!";
            expectedCompany = "dontAsk";
            break;
        case "withoutNumberPassword":
            expectedPassword = "Password!";
            expectedCompany = "dontAsk";
            break;
        case "withoutSpecialCharacterPassword":
            expectedPassword = "Password1";
            expectedCompany = "dontAsk";
            break;
        case "confirmationPassword":
            expectedConfirmPassword = "";
            expectedPassword = "Password1@";
            break;
    }
}

需要修改的静态常量：

public static String expectedFirstName = "test";
public static String expectedLastname = "test";
public static String expectedWorkEmail = "abd@thank.you";
public static String expectedCompany = "dontAsk";
public static String expectedPassword = "Password1@";
public static String expectedConfirmPassword = "Password1@";

优化方案1：策略模式（高扩展性） #

把每个case的修改逻辑封装成独立的策略类，用Map关联参数和策略，后续新增场景只需要加策略类，不用修改原方法，符合开闭原则。

步骤1：定义策略接口 #

interface FieldUpdateStrategy {
    void update();
}

步骤2：实现各个策略类 #

比如针对firstName的策略：

class FirstNameStrategy implements FieldUpdateStrategy {
    @Override
    public void update() {
        expectedFirstName = "";
    }
}

针对lastName的策略：

class LastNameStrategy implements FieldUpdateStrategy {
    @Override
    public void update() {
        expectedLastname = "";
        expectedFirstName = "test";
    }
}

其他case的策略类以此类推，每个类对应一个case的逻辑。

步骤3：初始化策略映射并修改方法 #

// 静态初始化策略Map
private static final Map<String, FieldUpdateStrategy> STRATEGY_MAP = new HashMap<>();

static {
    STRATEGY_MAP.put("firstName", new FirstNameStrategy());
    STRATEGY_MAP.put("lastName", new LastNameStrategy());
    STRATEGY_MAP.put("email", new EmailStrategy());
    // 其他策略依次放入
}

public static void setMissingField(String missingField) {
    FieldUpdateStrategy strategy = STRATEGY_MAP.get(missingField);
    if (strategy != null) {
        strategy.update();
    }
    // 可选：处理未匹配的参数
}

优化方案2：枚举类（类型安全+结构清晰） #

把每个参数对应的修改逻辑放到枚举成员中，利用枚举的抽象方法实现不同逻辑，既保证类型安全，又避免零散的类。

实现代码 #

enum FieldUpdateEnum {
    FIRST_NAME("firstName") {
        @Override
        public void update() {
            expectedFirstName = "";
        }
    },
    LAST_NAME("lastName") {
        @Override
        public void update() {
            expectedLastname = "";
            expectedFirstName = "test";
        }
    },
    EMAIL("email") {
        @Override
        public void update() {
            expectedWorkEmail = "";
            expectedLastname = "test";
        }
    },
    // 其他枚举成员依次实现
    ;

    private final String fieldName;

    FieldUpdateEnum(String fieldName) {
        this.fieldName = fieldName;
    }

    public abstract void update();

    // 根据字段名获取枚举
    public static FieldUpdateEnum getByFieldName(String fieldName) {
        for (FieldUpdateEnum enumVal : values()) {
            if (enumVal.fieldName.equals(fieldName)) {
                return enumVal;
            }
        }
        return null;
    }
}

// 修改原方法
public static void setMissingField(String missingField) {
    FieldUpdateEnum enumVal = FieldUpdateEnum.getByFieldName(missingField);
    if (enumVal != null) {
        enumVal.update();
    }
}

优化方案3：重置默认值+局部修改（快速简化代码） #

观察现有逻辑，很多case里会重复设置某些字段为默认值，比如lastName在多个邮箱相关case里都设为"test"，company在密码相关case里都设为"dontAsk"。可以先统一重置所有字段为默认值，再只修改当前case需要变动的字段，大幅减少重复代码。

实现代码 #

// 先实现重置默认值的方法
private static void resetDefaults() {
    expectedFirstName = "test";
    expectedLastname = "test";
    expectedWorkEmail = "abd@thank.you";
    expectedCompany = "dontAsk";
    expectedPassword = "Password1@";
    expectedConfirmPassword = "Password1@";
}

// 修改原方法
public static void setMissingField(String missingField) {
    resetDefaults();
    switch (missingField) {
        case "firstName":
            expectedFirstName = "";
            break;
        case "lastName":
            expectedLastname = "";
            break;
        case "email":
            expectedWorkEmail = "";
            break;
        case "shortEmail":
            expectedWorkEmail = "12@yes";
            break;
        case "invalidEmail":
            expectedWorkEmail = "asb@@abc.com";
            break;
        case "company":
            expectedCompany = "";
            break;
        case "password":
            expectedPassword = "";
            break;
        case "shortPassword":
            expectedPassword = "12Aa@";
            break;
        case "withoutLowerCasePassword":
            expectedPassword = "PASSWORD1@";
            break;
        case "withoutUpperCasePassword":
            expectedPassword = "password1!";
            break;
        case "withoutNumberPassword":
            expectedPassword = "Password!";
            break;
        case "withoutSpecialCharacterPassword":
            expectedPassword = "Password1";
            break;
        case "confirmationPassword":
            expectedConfirmPassword = "";
            break;
    }
}

方案对比 #

• 策略模式：扩展性最强，新增场景无需修改原有业务代码，但会增加类的数量，适合后续有大量新增需求的场景。
• 枚举类：类型安全，结构紧凑，不用额外创建类，适合场景固定、变动较少的情况。
• 重置默认值方案：实现最简单，代码量最少，能快速简化现有代码，适合当前逻辑重复度高的场景。

内容的提问来源于stack exchange，提问作者nuzooo