Updated the pull request with my last comments, but extremely happy with the code. Kudos klimas7!
I created a job with the latest version available in the update center. Then updated the plug-in to the pull request code, and saving the job this is the only change in the config.xml file.
27d26
< <filterLength>1</filterLength>
49d47
< <filterLength>1</filterLength>
In this case, I had two parameters, a normal active choices, and then a reactive referencing the previous parameter. Everything worked fine. I added a final request for changes regarding the noise in the JS console, and we will have to rethink the text in the documentation later.
ioannis I read your previous comment now, when I came here to comment in the JIRA ticket. What do you think about this feature?
Simply put, it adds a new input box after the check box to enable filter. This option can be any value (we can add validation later, as even negative values are accepted), by default it is set to 1, and the user may set that to 3 (a good value I believe) or even 10, in cases where it is known that parameters will have a common prefix, for example. This will save processing time, and improve the general performance.
We may decide to move it (and maybe filter, or other options) under an Advanced section later.
Waiting for ioannis feedback, and klimas7 feedback on the pull request, in order to merge it. Next release in the first or second week of December.
Hi Boguslaw,
Thanks for explaining the pull request. Let's leave this issue open and assigned to me. I've started a development cycle for the plug-in and will try to include your contribution in the next release
Thanks again
Bruno