Ran into issues with node_has_term
condition from the Islandora mod…
#819
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.
…ule. It
always saves to the block and fails to evaluate to false. It should not save if
no value has been specified for term URI.
Found the following in
web/core/lib/Drupal/Core/Condition/ConditionPluginCollection.php
.When doing the comparison we have.
So the comparison fails and the configuration is stored and evaluated later
causing issues since it fails to pass evaluation.
Hence we need to change the default config to match the submitted values.
What does this Pull Request do?
Changes the defaults for
NodeHasTerm
to reflect the submitted values.What's new?
Example:
How should this be tested?
A description of what steps someone could take to:
devel
After change is applied the configuration is not persisted.
Additional Notes:
This will not remove persisted configuration that already exists without a value as
===
is used in core for the comparison of the configuration, and that takes the order of values into account, and that configuration will not match the defaults asuri
was appended to the structure afterwards.