Occasionally, Schema.org may not include a needed property or field. When a Schema.org type is created, custom fields could be included.
Allow custom fields (not mapped to Schema.org) to be added to a mapping
Below are modules that create custom or additional fields when a Schema.org mapping is created.
Here is an example of a hook that could add a custom field.
/**
* Implements hook_schemadotorg_mapping_defaults_alter().
*/
function MODULE_schemadotorg_mapping_defaults_alter(array &$defaults, string $entity_type_id, ?string $bundle, string $schema_type): void {
if ($entity_type_id === 'node') {
$defaults['properties']['field_custom'] = [
'name' => 'field_custom',
'type' => 'string',
'label' => 'Custom',
];
}
}
Notes
Custom fields are being stored via the mapping.
Custom fields are not displayed via the mapping UI unless a module creates a UI. (i.e. subtype and layout)
Custom fields will be displayed.
Custom fields will be supported.
Custom field can be included in starterkit's mapping defaults.
Fixed
1.0
Code
Issue #3373574: Allow custom fields (not mapped to Schema.org) to be...
Automatically closed - issue fixed for 2 weeks with no activity.