Okay, a little disappointing, but the more I think about it, I think i was making things super complicated just for the fun of playing with the shiny features.
I'll just do an advanced box, and list each filter as a normal form component instead of a list of filters. Thanks On Thursday, February 12, 2026 at 7:56:02 AM UTC-8 [email protected] wrote: > Last I checked, `validate*` and `fill*` and `complete*` endpoints do not > support structured data. `@RelativePath` may not work in all cases either. > So if you were planning to use this filter list to dynamically constrain a > huge list of potential images to a small enough number to fit into a combo > box, I do not think this can work. > > The best you could do is offer a list of images based on the *last-saved* > filter > list, so the user would need to configure filters, save, then go back and > reconfigure the plugin to select images based on those filters. > > I would not recommend trying to write custom JS for this use case. You > could probably make it work, but it is going to be fragile in the face of > core changes. KISS > > CONFIDENTIALITY NOTICE: This email and any attachments contain > confidential and proprietary information of CloudBees intended only for the > named recipient(s). Unauthorized use or distribution is prohibited. If you > received this in error, please notify the sender and delete this email. -- 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 visit https://groups.google.com/d/msgid/jenkinsci-dev/6ee5e91b-d2fc-4f37-b739-d4eaae8e7710n%40googlegroups.com.
