Problem/Motivation
When I add the last_updated field, Config Inspector reports schema errors
display.default.display_options.fields.last_updated.date_format
display.default.display_options.fields.last_updated.custom_date_format
display.default.display_options.fields.last_updated.timezone
Steps to reproduce
1. Create a view, for example use nodes
2. Add the field "Comment Statistics: Updated/commented date"
3. Save the view
4. In the Config Inspector module, see schema errors for this view
Proposed resolution
Change views_field to views.field.date in the comment.views.schema.yml file
Comments
Comment #3
ivnishComment #4
smustgrave commentedMakes sense, it's what the rest of the date schemas are too.
Comment #5
astonvictor commented+1 RTBC
Comment #6
xjmI am trying to understand how this has been wrong for 11 years.
Is there a way we can validate the whole file?
Comment #7
catchWe don't have a way to validate config schema files, it would need some kind of config schema schema (not sure if I am half joking here or not). We can validate config against the schema and that will tell us if there's a mis-match but it could be either the config or schema that is wrong.
Might be something we're able to do eventually but I think we should just go ahead here.
Committed/pushed to 11.x and cherry-picked to 11.3.x, thanks!