Quoting @szeidler at #2921612: DateTimeEnhancer only work with Unix Timestamp fields → :
Unfortunately it seems, that we do not have information about the field type at that time of processing, but as an workaround we might assume, that numeric values are timestamps.
This … sounds like a huge flaw in the @ResourceFieldEnhancer concept.
For pure structure-based enhancers like \Drupal\jsonapi_extras\Plugin\jsonapi\FieldEnhancer\SingleNestedEnhancer, it makes sense to not be associated with a field type. But for most others, it doesn't make sense:
\Drupal\jsonapi_extras\Plugin\jsonapi\FieldEnhancer\DateTimeEnhancer\Drupal\jsonapi_extras\Plugin\jsonapi\FieldEnhancer\DateTimeFromStringEnhancer\Drupal\jsonapi_extras\Plugin\jsonapi\FieldEnhancer\UuidLinkEnhancerA consequence is that without field type information, these field enhancers also cannot automatically update API docs such as https://www.drupal.org/project/openapi → (marking critical for this reason).
TBD
Closed: won't fix
1.0
Code
Enhances developer experience.
Primarily changes documentation, not code. For Drupal core issues, select the Documentation component instead of using this tag. In general, component selection is preferred over tag selection.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
> If you have a textfield that contains an unix timestamp field, you should be able to enhance it.
True.
But some enhancers do expect a specific field type. E.g. the EntityShareUuidLinkEnhancer in Entity Share module expects to find a 'uri' property.
So *some* enhancers could specify a field type, and some could be universal.