Pattern::isFieldVisible returns false on valid mappings by using field instead of id #338
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.
Drupal\ui_patterns_views\Plugin\views\row\Pattern::isFieldVisible returns false on valid mappings. This is caused by using different identifiers for mapping and visiblity check.
Problem
These values are usually the same in views, but don't have to be. This can cause fields to not be passed to patterns.
How to reproduce
We had this bug with the field "Published on" provided by drupal/publication_date.
Sample from a view config
fields:
published_at:
id: published_at
table: node_field_data
field: published_at
published_at_1:
id: published_at_1
table: node_field_data
field: published_at
published_at_2:
id: published_at_2
table: node_field_data
field: published_at
Solution
Pass field id to isFieldVisible along with field. See changes in the PR.