Most field types in core have configuration schema to describe the properties, and the mapping matches with the properties.
- field.value.string (value)
- field.value.link (title, uri, options)
- field.value.string_long (value)
- field.value.text (value, format)
etc.
The datetime and daterange schema definitions however don't follow this pattern.
field.value.datetime:
type: mapping
label: 'Default value'
mapping:
default_date_type:
type: string
label: 'Default date type'
default_date:
type: string
label: 'Default date value'
I'm wondering whether this is by design or is there something missing still?
I'm asking this because the Conditional Fields module is trying to use the schema of the field type to set the conditions of a field. See https://www.drupal.org/project/conditional_fields/issues/3137764 →
It seems that we can use most of the field types but the datetime field we cannot use because of missing description of properties.
Thank you
Closed: works as designed
11.0 🔥
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I am closing this support request because there have been no recent comments.
The Drupal Core issue queue is not the ideal place for support requests. The 'support request' option is there for filing support issues for contributed modules and themes. There are several support options listed on our support page → (Community > Support at the top of Drupal.org) and there is Drupal Slack → . You may get better replies in one of those places.
