Sent from Mail for Windows 10

From: Rathinavelu
Sent: Sunday, A= pril 26, 2020 5:29 AM
To: users@groovy.apache.org
Subject: RE: Re: Strategy for opt= ionally excluding a named method parameter?

<= o:p>

Sirs,

1.We need both named parameters implemented through <= b>map and, also varags if we want to call with different numbers= of arguments, here 25 as well as 24.

var= ags has the syntax

def foo(Object... args) // same as de= f foo(Object[] args)

&nb= sp;

2.As for . =E2=80=A6What = we've discovered from testing is that if we send a value as either "tr= ue" or "false", it acts as if we sent "true".&= nbsp;=E2=80=A6 for me it does not happen; I get the correct response = as below.

= def g(Map map){ println !map.one} // I have complemented the p= assed parameter ! map.one

&= nbsp; g(one:false)

= g(one:true)

= The output is :

&n= bsp; true

= false

Thanking you,

T.Rathinavelu

Sent from Mail for Windows 10

From: MG
Sent: Sunday, Apri= l 26, 2020 5:00 AM
To: users@groovy.apache.org; David Karr
Subject: Re: Strategy for optionally excluding a = named method parameter?

= ;

Hi David,
since, as was mentioned, named parameters are implemented as a map und= erneath in Groovy, you should be able to remove the map entry of the parame= ter you do not want to pass, though I did not try this myself...

Che= ers,
mg

On 25/04/2020 20:57, Dav= id Karr wrote:

= On Sat, Apr 25, 2020 at 2:00 AM Rathinavelu <rathinavelu@gmail.com> wrote:
Named parameters are not avai= lable in Groovy, say, as in Python., though they say it is. Groovy has only= mapped parameters. The earlier mail works for a single =E2=80=98named=E2= =80=99 parameter; if there are more parameters Groovy does not work as =E2= =80=98expected=E2=80=99; it treats them only as positional parameters.=
Kindly mail me an use-case.<= /p>
T.Rathinavelu

The code sample looks something like this:

    functionName param1: value,
        param2: v= alue,
    = ;    param3: value,
        param4: value,<= /p>
      &nbs= p; ...
   &nbs= p;    param25: value

For instance, w= e need to make either the previous call or the following:

    functionName param1: value,
<= /div>
        p= aram2: value,
  &nb= sp;     param3: value,
        ...
        param25: v= alue

Where the "param4" key and value are= not provided. Presently, we have an "if" checking for a co= ndition, followed by the "true" block with the first version of t= he function call with 25 parameters, followed by the "else" and t= he "false" block with the second version, which has 24 parameters= , all the same values as in the first block, except for the one key and val= ue not provided in the second version.

Sent from = Mail for Windows 10
<= o:p>
From: David Karr
Sent: Saturday, April 25, 2020 1:48 AM
To: users@groovy.apache.org
Subject= : Strategy for optionally excluding a named method parameter?

Lately my only Groovy work is scripted pipelines in= Jenkins, version 2.89.4 .

I'm working wi= th an api that is somewhat dumb in one respect. The method we call ta= kes ~25 parameters. We send them as named parameters. One of the para= meters is of boolean type. What we've discovered from testing is that= if we send a value as either "true" or "false", it act= s as if we sent "true". If we construct the call without th= at parameter entirely, it acts as if we sent "false". I tried mak= ing it send null, but that just causes it to fail at runtime. We pres= ently have an "if" for that one flag, with two calls to the metho= d, one taking 25 parameters, the other taking 24. It is really obnoxi= ous.

Obviously, the proper fix is to chan= ge their api so that it works correctly. The reality is, that's not g= oing to happen any time soon in geological terms.
=

Is there a concise groovy syntax we could use that would optionall= y include or exclude a single parameter to the method?
=

&= nbsp;

=