groovy-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rathinavelu <>
Subject RE: Strategy for optionally excluding a named method parameter?
Date Sat, 25 Apr 2020 09:00:34 GMT
<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word"
xmlns:m="" xmlns=""><head><meta
http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft
Word 15 (filtered medium)"><style><!--
/* Font Definitions */
	panose-1:2 11 6 4 2 2 2 2 2 4;}
	{font-family:"Cambria Math";
	panose-1:2 4 5 3 5 4 6 3 2 4;}
	panose-1:2 15 5 2 2 2 4 3 2 4;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
a:link, span.MsoHyperlink
@page WordSection1
	{size:8.5in 11.0in;
	margin:1.0in 1.0in 1.0in 1.0in;}
--></style></head><body lang=EN-US link=blue vlink="#954F72"><div
class=WordSection1><p class=MsoNormal>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 ‘named’ parameter; if there are more parameters Groovy does not
work as ‘expected’; it treats them only as positional parameters.</p><p class=MsoNormal>Kindly
mail me an use-case.</p><p class=MsoNormal>T.Rathinavelu</p><p class=MsoNormal><o:p>&nbsp;</o:p></p><p
class=MsoNormal>Sent from <a href="">Mail</a>
for Windows 10</p><p class=MsoNormal><o:p>&nbsp;</o:p></p><div
style='mso-element:para-border-div;border:none;border-top:solid #E1E1E1 1.0pt;padding:3.0pt
0in 0in 0in'><p class=MsoNormal style='border:none;padding:0in'><b>From: </b><a
href="">David Karr</a><br><b>Sent: </b>Saturday,
April 25, 2020 1:48 AM<br><b>To: </b><a href=""></a><br><b>Subject:
</b>Strategy for optionally excluding a named method parameter?</p></div><p
class=MsoNormal>Lately my only Groovy work is scripted pipelines in Jenkins, version 2.89.4
.</p></div><div><p class=MsoNormal><o:p>&nbsp;</o:p></p></div><div><p
class=MsoNormal>I'm working with an api that is somewhat dumb in one respect.&nbsp;
The method we call takes ~25 parameters.&nbsp; We send them as named parameters. One of
the parameters is of boolean type.&nbsp; What we've discovered from testing is that if
we send a value as either &quot;true&quot; or &quot;false&quot;, it acts as
if we sent &quot;true&quot;.&nbsp; If we construct the call without that parameter
entirely, it acts as if we sent &quot;false&quot;. I tried making it send null, but
that just causes it to fail at runtime.&nbsp; We presently have an &quot;if&quot;
for that one flag, with two calls to the method, one taking 25 parameters, the other taking
24.&nbsp; It is really obnoxious.</p></div><div><p class=MsoNormal><o:p>&nbsp;</o:p></p></div><div><p
class=MsoNormal>Obviously, the proper fix is to change their api so that it works correctly.&nbsp;
The reality is, that's not going to happen any time soon in geological terms.</p></div><div><p
class=MsoNormal>Is there a concise groovy syntax we could use that would optionally include
or exclude a single parameter to the method?</p></div></div></div><p
class=MsoNormal><o:p>&nbsp;</o:p></p><p class=MsoNormal><o:p>&nbsp;</o:p></p></div></body></html>

View raw message