public AutoCompletionCandidates doAutoCompleteProjectId(
@AncestorInPath Jenkins context,
@QueryParameter("projectId") final String projectId,
@QueryParameter("credentialsId") final String credentialsId)
When I look at the requests generated in my plugin, I see requests like this:
http://.../descriptorByName/<descriptor name>/autoCompleteProjectId?value=asdf
However for the form validation doCheckProjectId which uses the same query parameters I see requests like this:
http://.../descriptorByName/<descriptor name>/checkProjectId?value=asdf&projectId=asdf&credentialsId=...
The behavior of doFillXXXItems is the same as doCheckXXX in that I can specify other query parameters which are
other entries in the same form, and update the contents of the drop down dynamically. I'd like to be able to determine
the autocomplete candidates in a similar way, but right now the end result is that the Stapler response body has an
empty list of suggestions because my method returns an and empty list when the credentialsId is null.
I'm trying to figure out what the source of this discrepancy is. I understand that this uses the YUI autocomplete feature
and I have a hunch that this fact is a huge part of the answer. I searched the jenkinsci organization on github and it
seems that almost no one has deviated from using the query parameter "value", and the one that I saw did not use more
than one query parameter. When I look up "jenkins autocomplete" I find references in various forms to the ui-samples plugin
above, or to JIRA issues about preventing auto completion of secure fields.
If anyone else has tried to dynamically update the autocomplete candidates based on other entries in a form that would be
helpful. I'd also be happy to hear a definitive "no, this functionality is not supported at the moment", file a feature request, and
go back to using a drop down but that isn't ideal. Taking a step back, it would be nice to have "doFillXXX" for textboxes based
on other fields in a form but that is something I do know isn't supported.