You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
I think you're misunderstanding the populateOption argument. If you just want a dropdown of options, use the option type. populateOption is for populating another argument with the value that you select. It should be accompanied by a target field. Take a look at https://github.com/gchq/CyberChef/blob/master/src/core/operations/RegularExpression.mjs for an example.
I wouldn't expect you to actually try to read the value of the populateOption argument itself, but rather the argument that it populates.
Given a configuration object that looks like:
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, changingname: 'none'
toname: 'None'
appears to break the script, whereas I believe it is likely intended to be only a visual change.The text was updated successfully, but these errors were encountered: