Workaround for Apex switch bug when multiple values and one of them is null?












8














The switch returns the wrong value for null for this case where there are multiple when values and one of them is null in API 43.0:



@IsTest
static void test() {
// Desired outcomes
System.assertEquals(1, f('a'));
System.assertEquals(2, f('b'));
System.assertEquals(2, f('c'));
System.assertEquals(3, f('d'));
System.assertEquals(0, f(''));
System.assertEquals(0, f(null)); // Fails
}

private static Integer f(String s) {
// Incorrectly returns 3 for null
switch on s {
when null, '' { return 0; }
when 'a' { return 1; }
when 'b', 'c' { return 2; }
when else { return 3; }
}
}


Is there a workaround for this?










share|improve this question
























  • I don't suppose you've logged a bug for this? I'm sure @ca_peterson would love to know about this (if he doesn't already).
    – sfdcfox
    yesterday










  • @sfdcfox If you mean via a case, sure I'll do that next week unless someone says it is already known.
    – Keith C
    yesterday
















8














The switch returns the wrong value for null for this case where there are multiple when values and one of them is null in API 43.0:



@IsTest
static void test() {
// Desired outcomes
System.assertEquals(1, f('a'));
System.assertEquals(2, f('b'));
System.assertEquals(2, f('c'));
System.assertEquals(3, f('d'));
System.assertEquals(0, f(''));
System.assertEquals(0, f(null)); // Fails
}

private static Integer f(String s) {
// Incorrectly returns 3 for null
switch on s {
when null, '' { return 0; }
when 'a' { return 1; }
when 'b', 'c' { return 2; }
when else { return 3; }
}
}


Is there a workaround for this?










share|improve this question
























  • I don't suppose you've logged a bug for this? I'm sure @ca_peterson would love to know about this (if he doesn't already).
    – sfdcfox
    yesterday










  • @sfdcfox If you mean via a case, sure I'll do that next week unless someone says it is already known.
    – Keith C
    yesterday














8












8








8







The switch returns the wrong value for null for this case where there are multiple when values and one of them is null in API 43.0:



@IsTest
static void test() {
// Desired outcomes
System.assertEquals(1, f('a'));
System.assertEquals(2, f('b'));
System.assertEquals(2, f('c'));
System.assertEquals(3, f('d'));
System.assertEquals(0, f(''));
System.assertEquals(0, f(null)); // Fails
}

private static Integer f(String s) {
// Incorrectly returns 3 for null
switch on s {
when null, '' { return 0; }
when 'a' { return 1; }
when 'b', 'c' { return 2; }
when else { return 3; }
}
}


Is there a workaround for this?










share|improve this question















The switch returns the wrong value for null for this case where there are multiple when values and one of them is null in API 43.0:



@IsTest
static void test() {
// Desired outcomes
System.assertEquals(1, f('a'));
System.assertEquals(2, f('b'));
System.assertEquals(2, f('c'));
System.assertEquals(3, f('d'));
System.assertEquals(0, f(''));
System.assertEquals(0, f(null)); // Fails
}

private static Integer f(String s) {
// Incorrectly returns 3 for null
switch on s {
when null, '' { return 0; }
when 'a' { return 1; }
when 'b', 'c' { return 2; }
when else { return 3; }
}
}


Is there a workaround for this?







apex






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited yesterday







Keith C

















asked yesterday









Keith CKeith C

94.6k1089203




94.6k1089203












  • I don't suppose you've logged a bug for this? I'm sure @ca_peterson would love to know about this (if he doesn't already).
    – sfdcfox
    yesterday










  • @sfdcfox If you mean via a case, sure I'll do that next week unless someone says it is already known.
    – Keith C
    yesterday


















  • I don't suppose you've logged a bug for this? I'm sure @ca_peterson would love to know about this (if he doesn't already).
    – sfdcfox
    yesterday










  • @sfdcfox If you mean via a case, sure I'll do that next week unless someone says it is already known.
    – Keith C
    yesterday
















I don't suppose you've logged a bug for this? I'm sure @ca_peterson would love to know about this (if he doesn't already).
– sfdcfox
yesterday




I don't suppose you've logged a bug for this? I'm sure @ca_peterson would love to know about this (if he doesn't already).
– sfdcfox
yesterday












@sfdcfox If you mean via a case, sure I'll do that next week unless someone says it is already known.
– Keith C
yesterday




@sfdcfox If you mean via a case, sure I'll do that next week unless someone says it is already known.
– Keith C
yesterday










1 Answer
1






active

oldest

votes


















8














One workaround is to separate the values. All the asserts pass for this code:



private static Integer f(String s) {
// Correctly returns 0 for null
switch on s {
when null { return 0; }
when '' { return 0; }
when 'a' { return 1; }
when 'b', 'c' { return 2; }
when else { return 3; }
}
}





share|improve this answer























    Your Answer








    StackExchange.ready(function() {
    var channelOptions = {
    tags: "".split(" "),
    id: "459"
    };
    initTagRenderer("".split(" "), "".split(" "), channelOptions);

    StackExchange.using("externalEditor", function() {
    // Have to fire editor after snippets, if snippets enabled
    if (StackExchange.settings.snippets.snippetsEnabled) {
    StackExchange.using("snippets", function() {
    createEditor();
    });
    }
    else {
    createEditor();
    }
    });

    function createEditor() {
    StackExchange.prepareEditor({
    heartbeatType: 'answer',
    autoActivateHeartbeat: false,
    convertImagesToLinks: false,
    noModals: true,
    showLowRepImageUploadWarning: true,
    reputationToPostImages: null,
    bindNavPrevention: true,
    postfix: "",
    imageUploader: {
    brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
    contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
    allowUrls: true
    },
    onDemand: true,
    discardSelector: ".discard-answer"
    ,immediatelyShowMarkdownHelp:true
    });


    }
    });














    draft saved

    draft discarded


















    StackExchange.ready(
    function () {
    StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f245572%2fworkaround-for-apex-switch-bug-when-multiple-values-and-one-of-them-is-null%23new-answer', 'question_page');
    }
    );

    Post as a guest















    Required, but never shown

























    1 Answer
    1






    active

    oldest

    votes








    1 Answer
    1






    active

    oldest

    votes









    active

    oldest

    votes






    active

    oldest

    votes









    8














    One workaround is to separate the values. All the asserts pass for this code:



    private static Integer f(String s) {
    // Correctly returns 0 for null
    switch on s {
    when null { return 0; }
    when '' { return 0; }
    when 'a' { return 1; }
    when 'b', 'c' { return 2; }
    when else { return 3; }
    }
    }





    share|improve this answer




























      8














      One workaround is to separate the values. All the asserts pass for this code:



      private static Integer f(String s) {
      // Correctly returns 0 for null
      switch on s {
      when null { return 0; }
      when '' { return 0; }
      when 'a' { return 1; }
      when 'b', 'c' { return 2; }
      when else { return 3; }
      }
      }





      share|improve this answer


























        8












        8








        8






        One workaround is to separate the values. All the asserts pass for this code:



        private static Integer f(String s) {
        // Correctly returns 0 for null
        switch on s {
        when null { return 0; }
        when '' { return 0; }
        when 'a' { return 1; }
        when 'b', 'c' { return 2; }
        when else { return 3; }
        }
        }





        share|improve this answer














        One workaround is to separate the values. All the asserts pass for this code:



        private static Integer f(String s) {
        // Correctly returns 0 for null
        switch on s {
        when null { return 0; }
        when '' { return 0; }
        when 'a' { return 1; }
        when 'b', 'c' { return 2; }
        when else { return 3; }
        }
        }






        share|improve this answer














        share|improve this answer



        share|improve this answer








        edited yesterday

























        answered yesterday









        Keith CKeith C

        94.6k1089203




        94.6k1089203






























            draft saved

            draft discarded




















































            Thanks for contributing an answer to Salesforce Stack Exchange!


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.





            Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


            Please pay close attention to the following guidance:


            • Please be sure to answer the question. Provide details and share your research!

            But avoid



            • Asking for help, clarification, or responding to other answers.

            • Making statements based on opinion; back them up with references or personal experience.


            To learn more, see our tips on writing great answers.




            draft saved


            draft discarded














            StackExchange.ready(
            function () {
            StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsalesforce.stackexchange.com%2fquestions%2f245572%2fworkaround-for-apex-switch-bug-when-multiple-values-and-one-of-them-is-null%23new-answer', 'question_page');
            }
            );

            Post as a guest















            Required, but never shown





















































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown

































            Required, but never shown














            Required, but never shown












            Required, but never shown







            Required, but never shown







            Popular posts from this blog

            1300-talet

            1300-talet

            Display a custom attribute below product name in the front-end Magento 1.9.3.8