Both named and varag

def f(= Object[] args){ println args.one

print args.two }

f(one: "string",two:false)

f(one:"string", two:true)

f(two:= false)

f(two:true)

f(two: 1= =3D=3D2)

f(two: 1=3D=3D1)

f= (two: 1=3D=3D2)

[string]

[false][string]

[true][null]

[false][null]

[true][null]

[false][null]

[true][null]

[false]

<= o:p>

Please as a work around keep the <= b>boolean as the last parameter. Since map is a subclass of =C2= =A0Object, the function polymorphically accepts map object . = But why Boolean be the last to work? Sorry, Sir! I am into groovy only from= last week! A long way to go!

The reason for always= =E2=80=98false=E2=80=99 in the middle perhaps =C2=A0is =E2=80=9Cinvisible = input=E2=80=9D. Last output has no [null]

T.Rathina= velu

Sent= from Mail= for Windows 10

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

&n= bsp;

Hi David,=

since, as was mentioned, named parameters are implemented as a map = underneath in Groovy, you should be able to remove the map entry of the par= ameter you do not want to pass, though I did not try this myself...

= Cheers,
mg

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

On Sat, Apr 25, 2020 at 2:00 AM Rathinavelu <rathinavelu@gmail.com> wrote:<= /p>
Named parameters are not available 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 parameter= s Groovy does not work as =E2=80=98expected=E2=80=99; it treats them only a= s positional parameters.
Kindly mail me an use-case.
T= .Rathinavelu
&nb= sp;
The code sample looks somethin= g like this:

    functionName param1= : value,
   &n= bsp;    param2: value,
        param3: value,
      &= nbsp; param4: value,
&n= bsp;      ...
        param25: value

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

    functionName= param1: value,
  &= nbsp;     param2: value,
        param3: value,
      = ; ...
   &nbs= p;    param25: value

Where the "= ;param4" key and value are not provided. Presently, we have an &= quot;if" checking for a condition, followed by the "true" bl= ock with the first version of the function call with 25 parameters, followe= d by the "else" and the "false" block with the second v= ersion, which has 24 parameters, all the same values as in the first block,= except for the one key and value not provided in the second version.<= /o:p>

<= blockquote style=3D'border:none;border-left:solid #CCCCCC 1.0pt;padding:0in= 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'>
<= /p>
Sent from Mail for Windows 10

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?

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

I'm working with an api = that is somewhat dumb in one respect. The method we call takes ~25 pa= rameters. We send them as named parameters. One of the parameters is = of boolean type. What we've discovered from testing is that if we sen= d a value as either "true" or "false", it acts as if we= sent "true". If we construct the call without that paramet= er entirely, it acts as if we sent "false". I tried making it sen= d null, but that just causes it to fail at runtime. We presently have= an "if" for that one flag, with two calls to the method, one tak= ing 25 parameters, the other taking 24. It is really obnoxious.

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

Is there a concise groovy syntax we could use = that would optionally include or exclude a single parameter to the method?<= /p>