Quantcast
Channel: Issues for Drupal core
Viewing all articles
Browse latest Browse all 298090

time_diff 'description' field not propagated to existing core views, view tests or core schema after being added to TimestampFormatter

$
0
0

Updated as of comment #20

Problem/Motivation

In #2921810: Allow TimestampFormatter to show as a fully cacheable time difference with JS, a time diff formatting option is provided. Part of that implementation was a "fallback configuration", labeled 'description'. No config schema was added for description, leading to situations where my CI build fails that validates configuration.

Steps to reproduce

Have schema validator enabled; add a timestamp field to a view; try saving the view. Expected: the view gets saved. Actual: a config schema validation exception is thrown.

Proposed resolution

Add schema for 'description' to Drupal core, core views and test views. (the MR does this).

Remaining tasks

Investigate and determine cause of failures mentioned in comment #16.

User interface changes

None.

API changes

None.

Data model changes

None.

Release notes snippet

TBD.


Viewing all articles
Browse latest Browse all 298090

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>