Bug: populationOption type seems to ignore value #347
Description
Given a configuration object that looks like:
{
name: "Signing Algorithm",
type: "populateOption",
value: [
{
name: "HS256",
value: "HS256"
},
{
name: "HS384",
value: "HS384",
},
...When the user selects from the dropdown one with a name of 'None' but a value of 'none', I still appear to get 'None' back as the value.
PoC of this can be seen in the jwt pull request, changing name: 'none' to name: 'None' appears to break the script, whereas I believe it is likely intended to be only a visual change.