There could be optional ordinal field for DataBoundSetter and annotation 
for constructor parameters to support ordering, but it would require a 
patch in a foundation Jenkins libs like structs.

BR, Oleg

On Saturday, August 11, 2018 at 3:57:18 PM UTC+2, Jesse Glick wrote:
>
> On Sat, Aug 11, 2018 at 5:53 AM Martin Weber <enten...@gmx.de 
> <javascript:>> wrote: 
> > Could the snippetizer be changed to derive the parameter order from the 
> UI (jelly file)? 
>
> Uh, this would be quite hacky as you would have to not just parse that 
> XML but hard-code knowledge of how various databinding controls encode 
> the name of a parameter—sometimes a `field` on a `section`, sometimes 
> directly on a control. And then there are config forms which for 
> various reasons directly refer to `${instance.fieldName}` or similar. 
> And it would not work at all for Groovy views. 
>
> I did track down a possible mistake in the current code: 
> https://issues.jenkins-ci.org/browse/JENKINS-52996 
>

-- 
You received this message because you are subscribed to the Google Groups 
"Jenkins Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to jenkinsci-dev+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/jenkinsci-dev/33aa780d-8926-491b-b275-7e5e0a76a5ea%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to