[FEATURE] Improve the usability of the actual value selection process about rest-list-parameter-plugin HOT 7 CLOSED

You may want to keep an eye on JENKINS-62024 and jenkins/pull/4688. That implementation will probably satisfy the request.

from rest-list-parameter-plugin.

from rest-list-parameter-plugin.

Thank you for the heads up 👍 Unfortunately, given the activity in that PR, it might take some time for the core team to merge it.
I might have a look and see if I can take anything from it and build my own version 🤔

from rest-list-parameter-plugin.

@ianwilliams1, sorry for the ping, but would be something like a datalist element be enough to fulfill this requirement in your opinion?
I finally have some time on my hands again and am trying to get this in whilst preparing for the new div based UI of the core.

from rest-list-parameter-plugin.

I knew about the IE and legacy Edge limitations, but good call with the mailing list I will give that one a shot.

from rest-list-parameter-plugin.

Oh boy. Warning, this might sound like a rant. (there is a TLDR at the end)

I have now "played" around with this for about 2 days, to get absolutely nowhere ☹️.
That what I have got working is unusable from a UX perspective and I am not going to start commenting on my mess of a code (JS code mind you).
I am pulling the emergency shoot right now before I go into a meltdown over how much I dislike doing web front ends without good documentation or a supportive framework (e.g. Angular, Vue, ...).
DISCLAIMER: I not solely ended using datalist due to UX problems that even I could not bear with and tried several approaches to "improve it", a lot of building, deploying and a lot of me cussing over my own JS misery later and that what I got working is in no way better than what I started with.

TLDR:
I give up on using datalist or trying to implement a 'combobox' component on my own (no idea why I tried the latter) to save my sanity/motivation to keep going.

Next steps:
Well, as far as I can tell I have 2 options (and I don't particularly like either, despite preferring one over the other due to UX and design):

1. continue using a simple select component and add a filter input field that gets used with some JS to filter the select options. This should be a very straight forward solution, however I am no fan for the UI nor the UX of this solution.
2. use a 3rd party solution that offers a proper filterable select component (e.g. Select2). This approach should be as easy as it can be and I like its UI/UX more. However, I am unsure if this is an acceptable approach or would be playing along well with the Jenkins UI as a whole.

Regardless, I will take a break of this task till the weekend and select one of these approaches (most likely going to try both anyway). If you have any comment or input on this feel free to share it, I would definitively appreciate a second opinion.

from rest-list-parameter-plugin.

After long delay, and a couple of times I got distracted by other things, here a sneak peak on what i have (yes I am using select2)

from rest-list-parameter-plugin.