Feature/1572 relation field elements matching #1585
Merged
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.
Description
When mapping relation fields, for some relation field types, you can choose to map them not only via a predefined list of attributes but also some of the custom fields.
Historically, the list of available match options was a list of all the fields (not just ones that are related to the sections/category group, etc., that are used by the relation field) that were deemed fit to be used as a unique identifier (a selection of the “simple” fields).
With the changes in Craft 5, that has become less intuitive to use.
This PR changes this behaviour so that:
To be clear, in all the above cases, the list of fields is further filtered down to only the ones that can be used as a unique identifier.
Related issues
#1572