Is there a way in Ruby to make just any one out of many keyword arguments required? Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)Ruby on rails complex select statement…there has to be a better way!What if any design issues are there in this method of loading configuration data from YAML in Ruby?Is there a more succinct way to write this Ruby function?Are there any glaring issues with the way I write and test my Ruby classes?Pretty way of keeping sensitive info out of a logged command string in Ruby?Machi Koro card/dice game

How to recreate this effect in Photoshop?

How can whole tone melodies sound more interesting?

Is above average number of years spent on PhD considered a red flag in future academia or industry positions?

How can I fade player when goes inside or outside of the area?

Is the Standard Deduction better than Itemized when both are the same amount?

How to say 'striped' in Latin

What LEGO pieces have "real-world" functionality?

Is 1 ppb equal to 1 μg/kg?

Date formating in QGIS expression

How discoverable are IPv6 addresses and AAAA names by potential attackers?

How to bypass password on Windows XP account?

What does the "x" in "x86" represent?

When is phishing education going too far?

How to draw this diagram using TikZ package?

Marking the functions of a sentence: 'She may like it'

How to motivate offshore teams and trust them to deliver?

Area of a 2D convex hull

Do I really need recursive chmod to restrict access to a folder?

Is there a way in Ruby to make just any one out of many keyword arguments required?

Sorting numerically

Antler Helmet: Can it work?

Why there are no cargo aircraft with "flying wing" design?

What do you call a plan that's an alternative plan in case your initial plan fails?

Why is black pepper both grey and black?



Is there a way in Ruby to make just any one out of many keyword arguments required?



Announcing the arrival of Valued Associate #679: Cesar Manara
Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)Ruby on rails complex select statement…there has to be a better way!What if any design issues are there in this method of loading configuration data from YAML in Ruby?Is there a more succinct way to write this Ruby function?Are there any glaring issues with the way I write and test my Ruby classes?Pretty way of keeping sensitive info out of a logged command string in Ruby?Machi Koro card/dice game



.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;








1












$begingroup$


I am trying to write a method, that works with three types of arguments, but requires only one of them.



def convert(arg_a: 1, arg_b: 2, arg_c: 'foo')
end


Please note, that both: arg_a, and arg_b are the same type (let's say Numeric), so using one mandatory argument, and then making decision based on the input type won't work here.



At this point my code looks like this:



def convert(arg_a: nil, arg_b: nil, arg_c: nil)
if arg_b.nil? && arg_c.nil? && arg_a
# do something with arg_a
elsif arg_a.nil? && arg_c.nil? && arg_b
# do something with arg_b
elsif arg_a.nil? && arg_b.nil? && arg_c
# do something with arg_c
else
raise ArgumentError
end


In my opinion this code smells a little, and can be improved. Any thoughts?










share|improve this question









$endgroup$



migrated from stackoverflow.com 3 hours ago


This question came from our site for professional and enthusiast programmers.
























    1












    $begingroup$


    I am trying to write a method, that works with three types of arguments, but requires only one of them.



    def convert(arg_a: 1, arg_b: 2, arg_c: 'foo')
    end


    Please note, that both: arg_a, and arg_b are the same type (let's say Numeric), so using one mandatory argument, and then making decision based on the input type won't work here.



    At this point my code looks like this:



    def convert(arg_a: nil, arg_b: nil, arg_c: nil)
    if arg_b.nil? && arg_c.nil? && arg_a
    # do something with arg_a
    elsif arg_a.nil? && arg_c.nil? && arg_b
    # do something with arg_b
    elsif arg_a.nil? && arg_b.nil? && arg_c
    # do something with arg_c
    else
    raise ArgumentError
    end


    In my opinion this code smells a little, and can be improved. Any thoughts?










    share|improve this question









    $endgroup$



    migrated from stackoverflow.com 3 hours ago


    This question came from our site for professional and enthusiast programmers.




















      1












      1








      1





      $begingroup$


      I am trying to write a method, that works with three types of arguments, but requires only one of them.



      def convert(arg_a: 1, arg_b: 2, arg_c: 'foo')
      end


      Please note, that both: arg_a, and arg_b are the same type (let's say Numeric), so using one mandatory argument, and then making decision based on the input type won't work here.



      At this point my code looks like this:



      def convert(arg_a: nil, arg_b: nil, arg_c: nil)
      if arg_b.nil? && arg_c.nil? && arg_a
      # do something with arg_a
      elsif arg_a.nil? && arg_c.nil? && arg_b
      # do something with arg_b
      elsif arg_a.nil? && arg_b.nil? && arg_c
      # do something with arg_c
      else
      raise ArgumentError
      end


      In my opinion this code smells a little, and can be improved. Any thoughts?










      share|improve this question









      $endgroup$




      I am trying to write a method, that works with three types of arguments, but requires only one of them.



      def convert(arg_a: 1, arg_b: 2, arg_c: 'foo')
      end


      Please note, that both: arg_a, and arg_b are the same type (let's say Numeric), so using one mandatory argument, and then making decision based on the input type won't work here.



      At this point my code looks like this:



      def convert(arg_a: nil, arg_b: nil, arg_c: nil)
      if arg_b.nil? && arg_c.nil? && arg_a
      # do something with arg_a
      elsif arg_a.nil? && arg_c.nil? && arg_b
      # do something with arg_b
      elsif arg_a.nil? && arg_b.nil? && arg_c
      # do something with arg_c
      else
      raise ArgumentError
      end


      In my opinion this code smells a little, and can be improved. Any thoughts?







      ruby






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked 3 hours ago









      ciejjciejj

      163




      163




      migrated from stackoverflow.com 3 hours ago


      This question came from our site for professional and enthusiast programmers.









      migrated from stackoverflow.com 3 hours ago


      This question came from our site for professional and enthusiast programmers.






















          2 Answers
          2






          active

          oldest

          votes


















          2












          $begingroup$

          There are lots of ways of improving this; at a high level, I'd say it's possible the method itself should be broken up into multiple methods with distinct names, because a method that accepts three different inputs and does three different things with them probably doesn't have a single responsibility.



          That not withstanding, you can clean this method up by separating the argument validation from the rest of the logic. There are lots of ways of doing this, but if you just need exactly one non-nil argument, you can use something along these lines:



          def convert(arg_a: nil, arg_b: nil, arg_c: nil)
          raise ArgumentError unless [arg_a, arg_b, arg_c].compact.one?

          if arg_a
          # do something with arg_a
          elsif arg_b
          # do something with arg_b
          elsif arg_c
          # do something with arg_c
          end
          end





          share|improve this answer











          $endgroup$












          • $begingroup$
            The solution proposed by you does makes the code much clearer - I think this is the answer I was looking for. This convert method is only for argument validation - based on it other methods are called.
            $endgroup$
            – ciejj
            2 hours ago



















          1












          $begingroup$

          From what I can tell, your implementation only makes use of one of the three arguments, and only really expects (or allows) a single argument at a time.



          i.e., with your current implementation, this is what an error-free call-site looks like:



          convert(arg_a: 1)
          convert(arg_b: 2)
          convert(arg_c: 'foo')


          If the method were called with two or more arguments (any of them), it would raise an ArgumentError, so really, this method can only be called with a single argument.



          Given that you're already using keyword arguments with a default value of nil, I cannot see how this is any better than simply writing three different methods that handle the three values. Therefore, something like...



          def convert_arg_a(a)
          # Handle a...
          end

          def convert_arg_b(b)
          # Handle b...
          end

          def convert_arg_c(c)
          # Handle c...
          end


          ...should be able to do exactly what is possible with the implementation you've described, with none of the branching.






          share|improve this answer








          New contributor




          Hari Gopal is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
          Check out our Code of Conduct.






          $endgroup$













            Your Answer






            StackExchange.ifUsing("editor", function ()
            StackExchange.using("externalEditor", function ()
            StackExchange.using("snippets", function ()
            StackExchange.snippets.init();
            );
            );
            , "code-snippets");

            StackExchange.ready(function()
            var channelOptions =
            tags: "".split(" "),
            id: "196"
            ;
            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%2fcodereview.stackexchange.com%2fquestions%2f217502%2fis-there-a-way-in-ruby-to-make-just-any-one-out-of-many-keyword-arguments-requir%23new-answer', 'question_page');

            );

            Post as a guest















            Required, but never shown

























            2 Answers
            2






            active

            oldest

            votes








            2 Answers
            2






            active

            oldest

            votes









            active

            oldest

            votes






            active

            oldest

            votes









            2












            $begingroup$

            There are lots of ways of improving this; at a high level, I'd say it's possible the method itself should be broken up into multiple methods with distinct names, because a method that accepts three different inputs and does three different things with them probably doesn't have a single responsibility.



            That not withstanding, you can clean this method up by separating the argument validation from the rest of the logic. There are lots of ways of doing this, but if you just need exactly one non-nil argument, you can use something along these lines:



            def convert(arg_a: nil, arg_b: nil, arg_c: nil)
            raise ArgumentError unless [arg_a, arg_b, arg_c].compact.one?

            if arg_a
            # do something with arg_a
            elsif arg_b
            # do something with arg_b
            elsif arg_c
            # do something with arg_c
            end
            end





            share|improve this answer











            $endgroup$












            • $begingroup$
              The solution proposed by you does makes the code much clearer - I think this is the answer I was looking for. This convert method is only for argument validation - based on it other methods are called.
              $endgroup$
              – ciejj
              2 hours ago
















            2












            $begingroup$

            There are lots of ways of improving this; at a high level, I'd say it's possible the method itself should be broken up into multiple methods with distinct names, because a method that accepts three different inputs and does three different things with them probably doesn't have a single responsibility.



            That not withstanding, you can clean this method up by separating the argument validation from the rest of the logic. There are lots of ways of doing this, but if you just need exactly one non-nil argument, you can use something along these lines:



            def convert(arg_a: nil, arg_b: nil, arg_c: nil)
            raise ArgumentError unless [arg_a, arg_b, arg_c].compact.one?

            if arg_a
            # do something with arg_a
            elsif arg_b
            # do something with arg_b
            elsif arg_c
            # do something with arg_c
            end
            end





            share|improve this answer











            $endgroup$












            • $begingroup$
              The solution proposed by you does makes the code much clearer - I think this is the answer I was looking for. This convert method is only for argument validation - based on it other methods are called.
              $endgroup$
              – ciejj
              2 hours ago














            2












            2








            2





            $begingroup$

            There are lots of ways of improving this; at a high level, I'd say it's possible the method itself should be broken up into multiple methods with distinct names, because a method that accepts three different inputs and does three different things with them probably doesn't have a single responsibility.



            That not withstanding, you can clean this method up by separating the argument validation from the rest of the logic. There are lots of ways of doing this, but if you just need exactly one non-nil argument, you can use something along these lines:



            def convert(arg_a: nil, arg_b: nil, arg_c: nil)
            raise ArgumentError unless [arg_a, arg_b, arg_c].compact.one?

            if arg_a
            # do something with arg_a
            elsif arg_b
            # do something with arg_b
            elsif arg_c
            # do something with arg_c
            end
            end





            share|improve this answer











            $endgroup$



            There are lots of ways of improving this; at a high level, I'd say it's possible the method itself should be broken up into multiple methods with distinct names, because a method that accepts three different inputs and does three different things with them probably doesn't have a single responsibility.



            That not withstanding, you can clean this method up by separating the argument validation from the rest of the logic. There are lots of ways of doing this, but if you just need exactly one non-nil argument, you can use something along these lines:



            def convert(arg_a: nil, arg_b: nil, arg_c: nil)
            raise ArgumentError unless [arg_a, arg_b, arg_c].compact.one?

            if arg_a
            # do something with arg_a
            elsif arg_b
            # do something with arg_b
            elsif arg_c
            # do something with arg_c
            end
            end






            share|improve this answer














            share|improve this answer



            share|improve this answer








            edited 2 hours ago

























            answered 3 hours ago









            meagarmeagar

            858513




            858513











            • $begingroup$
              The solution proposed by you does makes the code much clearer - I think this is the answer I was looking for. This convert method is only for argument validation - based on it other methods are called.
              $endgroup$
              – ciejj
              2 hours ago

















            • $begingroup$
              The solution proposed by you does makes the code much clearer - I think this is the answer I was looking for. This convert method is only for argument validation - based on it other methods are called.
              $endgroup$
              – ciejj
              2 hours ago
















            $begingroup$
            The solution proposed by you does makes the code much clearer - I think this is the answer I was looking for. This convert method is only for argument validation - based on it other methods are called.
            $endgroup$
            – ciejj
            2 hours ago





            $begingroup$
            The solution proposed by you does makes the code much clearer - I think this is the answer I was looking for. This convert method is only for argument validation - based on it other methods are called.
            $endgroup$
            – ciejj
            2 hours ago














            1












            $begingroup$

            From what I can tell, your implementation only makes use of one of the three arguments, and only really expects (or allows) a single argument at a time.



            i.e., with your current implementation, this is what an error-free call-site looks like:



            convert(arg_a: 1)
            convert(arg_b: 2)
            convert(arg_c: 'foo')


            If the method were called with two or more arguments (any of them), it would raise an ArgumentError, so really, this method can only be called with a single argument.



            Given that you're already using keyword arguments with a default value of nil, I cannot see how this is any better than simply writing three different methods that handle the three values. Therefore, something like...



            def convert_arg_a(a)
            # Handle a...
            end

            def convert_arg_b(b)
            # Handle b...
            end

            def convert_arg_c(c)
            # Handle c...
            end


            ...should be able to do exactly what is possible with the implementation you've described, with none of the branching.






            share|improve this answer








            New contributor




            Hari Gopal is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
            Check out our Code of Conduct.






            $endgroup$

















              1












              $begingroup$

              From what I can tell, your implementation only makes use of one of the three arguments, and only really expects (or allows) a single argument at a time.



              i.e., with your current implementation, this is what an error-free call-site looks like:



              convert(arg_a: 1)
              convert(arg_b: 2)
              convert(arg_c: 'foo')


              If the method were called with two or more arguments (any of them), it would raise an ArgumentError, so really, this method can only be called with a single argument.



              Given that you're already using keyword arguments with a default value of nil, I cannot see how this is any better than simply writing three different methods that handle the three values. Therefore, something like...



              def convert_arg_a(a)
              # Handle a...
              end

              def convert_arg_b(b)
              # Handle b...
              end

              def convert_arg_c(c)
              # Handle c...
              end


              ...should be able to do exactly what is possible with the implementation you've described, with none of the branching.






              share|improve this answer








              New contributor




              Hari Gopal is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
              Check out our Code of Conduct.






              $endgroup$















                1












                1








                1





                $begingroup$

                From what I can tell, your implementation only makes use of one of the three arguments, and only really expects (or allows) a single argument at a time.



                i.e., with your current implementation, this is what an error-free call-site looks like:



                convert(arg_a: 1)
                convert(arg_b: 2)
                convert(arg_c: 'foo')


                If the method were called with two or more arguments (any of them), it would raise an ArgumentError, so really, this method can only be called with a single argument.



                Given that you're already using keyword arguments with a default value of nil, I cannot see how this is any better than simply writing three different methods that handle the three values. Therefore, something like...



                def convert_arg_a(a)
                # Handle a...
                end

                def convert_arg_b(b)
                # Handle b...
                end

                def convert_arg_c(c)
                # Handle c...
                end


                ...should be able to do exactly what is possible with the implementation you've described, with none of the branching.






                share|improve this answer








                New contributor




                Hari Gopal is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.






                $endgroup$



                From what I can tell, your implementation only makes use of one of the three arguments, and only really expects (or allows) a single argument at a time.



                i.e., with your current implementation, this is what an error-free call-site looks like:



                convert(arg_a: 1)
                convert(arg_b: 2)
                convert(arg_c: 'foo')


                If the method were called with two or more arguments (any of them), it would raise an ArgumentError, so really, this method can only be called with a single argument.



                Given that you're already using keyword arguments with a default value of nil, I cannot see how this is any better than simply writing three different methods that handle the three values. Therefore, something like...



                def convert_arg_a(a)
                # Handle a...
                end

                def convert_arg_b(b)
                # Handle b...
                end

                def convert_arg_c(c)
                # Handle c...
                end


                ...should be able to do exactly what is possible with the implementation you've described, with none of the branching.







                share|improve this answer








                New contributor




                Hari Gopal is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.









                share|improve this answer



                share|improve this answer






                New contributor




                Hari Gopal is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.









                answered 2 hours ago









                Hari GopalHari Gopal

                1111




                1111




                New contributor




                Hari Gopal is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.





                New contributor





                Hari Gopal is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.






                Hari Gopal is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
                Check out our Code of Conduct.



























                    draft saved

                    draft discarded
















































                    Thanks for contributing an answer to Code Review 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.

                    Use MathJax to format equations. MathJax reference.


                    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%2fcodereview.stackexchange.com%2fquestions%2f217502%2fis-there-a-way-in-ruby-to-make-just-any-one-out-of-many-keyword-arguments-requir%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

                    Era Viking Índice Início da Era Viquingue | Cotidiano | Sociedade | Língua | Religião | A arte | As primeiras cidades | As viagens dos viquingues | Viquingues do Oeste e Leste | Fim da Era Viquingue | Fontes históricas | Referências Bibliografia | Ligações externas | Menu de navegação«Sverige då!»«Handel I vikingetid»«O que é Nórdico Antigo»Mito, magia e religião na volsunga saga Um olhar sobre a trajetória mítica do herói sigurd«Bonden var den verklige vikingen»«Vikingatiden»«Vikingatiden»«Vinland»«Guerreiras de Óðinn: As Valkyrjor na Mitologia Viking»1519-9053«Esculpindo símbolos e seres: A arte viking em pedras rúnicas»1679-9313Historia - Tema: VikingarnaAventura e Magia no Mundo das Sagas IslandesasEra Vikinge

                    What's the metal clinking sound at the end of credits in Avengers: Endgame?What makes Thanos so strong in Avengers: Endgame?Who is the character that appears at the end of Endgame?What happens to Mjolnir (Thor's hammer) at the end of Endgame?The People's Ages in Avengers: EndgameWhat did Nebula do in Avengers: Endgame?Messing with time in the Avengers: Endgame climaxAvengers: Endgame timelineWhat are the time-travel rules in Avengers Endgame?Why use this song in Avengers: Endgame Opening Logo Sequence?Peggy's age in Avengers Endgame

                    Are there legal definitions of ethnicities/races? The 2019 Stack Overflow Developer Survey Results Are In Announcing the arrival of Valued Associate #679: Cesar Manara Planned maintenance scheduled April 17/18, 2019 at 00:00UTC (8:00pm US/Eastern)Legal definitions in the United StatesAre there truly legal limits on US interest rates?Are gender identity and sexual orientation federally protected?Why is there an apparent legal bias against digital services?What limits are there to the powers of individual judges in the United States legal system?Are women only scholarships legal under Irish / EU law?Is the term “race” defined by Public Law enacted by Congress of the United StatesIs there a legal definition of race in the US?Neighbors are spying for landlord on Renters is it legal?Are Protected Classes Bi-directional?