LIBHYDRA-572. Updated ControlledURIRef to handle unsetting value #396
+9
−3
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
"insert" field when the user selects the "empty" option in drop-down
list.
This is done so that when the "empty" option is chosen, the
generated SPAQRL only contains a "DELETE" statement.
Prior to this change the SPARQL query should generate both a "DELETE"
statement, and an "INSERT" statement of the form:
which resulted in the being used for the node field.
This change fixes the validation issue seen in Plastron, because no
value is being inserted, so validator that checks whether the new value
is in the vocabulary is not triggered.
option that occurs when the initial value of field is the empty value.
This was occurring because the "empty" value is not in the vocabulary,
and so gets added to the vocabulary in the constructor, while the
React component template also contains an "empty" option field.
Modified the ControlledURIRef component so that the initial field value
does not get added to the vocabulary if it is an empty string.
https://umd-dit.atlassian.net/browse/LIBHYDRA-572