Follow-up from #1881606: Use a derivative to integrate all entities as row plugins.
Updated: Comment #N
Problem/Motivation
Colon (:) in config key makes config schema bit hard to read.
For non-entity row plugin has the schema like this:
views.row.rss_fields:
type: views_row
label: 'Field options'
mapping:
But the entity has schema like this:
"views.row.entity:node":
type: views_row
label: 'Field options'
mapping:
We need to use quotes to tell config schema that views.row.entity:node is one key and (not consider 'views.row.entity' as and 'node' as value)
Proposed resolution
1. Replace ':' with '.' if we can write schema like https://gist.github.com/vijaycs85/7845936#file-view-plugin-yml
2. Replace other non-entity elements to support this format (e.g. views.row.rss_fields need to be views.row.config.rss_field and views.row.fields need to be views.row.field.fields)
Remaining tasks
1. Discuss
2. Issue patch
User interface changes
No
API changes
No
Comments
Comment #1
vijaycs85Duplicate of #2035345: Reconsider whether to use ':' as separator for derivative plugins