Parsing / re-parsing issue for single string as extractor key input for UI form #1580
<
8000
div class="d-flex flex-order-2 flex-md-order-1 mx-2">
Labels
Comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
The following issue was discovered while helping M. Denslow in #notes-from-nature Slack channel (private link to Slack thread).
Although the default placeholder example suggests that the input for the
extractor_keysfilter parameter be an array of strings (e.g.,["extractor_1", "extractor_2", "extractor_3"]), the reducer form allows a single string to be input as well (e.g.,"extractor_1"). However, when that single string is read back in to the form for reducer config editing, it appears without quotes and when the form is submitted, the submission returns an error.The Sentry error clearly explains this is a JSON parsing issue, however the user only receives a vague, generic error: "We're sorry, but something went wrong."
If a single string value is going to be allowed, what change needs to be made such that when it is read back into the form during reducer editing that resubmission of the existing value will be allowed? Is this issue somehow related to how existing parameter settings are ready back into the form, as added in #1389?
The text was updated successfully, but these errors were encountered: