I am implementing reusable describable to be used on multiple places on
config page (in multiple depths from json perspective) but need to refer
to several other inputs (on predictable json depth) its relative path
can be different.
I was ready to chop it out of the json or even request parameters but
none of that is available unless the form was submitted or the
parameters with (correct relative path) are explicitly stated in the
signature.
I ended up doing something like:
```
@RelativePath("..") @QueryParameter String myField,
@RelativePath("../..") @QueryParameter("myField") String myField2,
...
```
for every parameter. Needless to say this is awful, poorly scalable and
fragile. (Though it works surprisingly well, Stapler will actually
populate the parameters corresponding to the inputs not found with
values of those that were found!)
Is there any better way?
Thanks
--
oliver
--
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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/jenkinsci-dev/56D74074.20303%40gmail.com.
For more options, visit https://groups.google.com/d/optout.
