- Issue created by @rudolfbyker
- 🇮🇳India Akhil Babu Chengannur
Thanks for the detailed issue decsription. I tried to recreate this issue wirh the given view configuration in Drupal 10.2.2 & Drupal 11 versions and these are the observations.
If custom date format is selected and 'U' is given as the format, Timestamp value of the date appeares correctly in the response.
If another custom date format is used (Eg: m/d/Y), date gets correctly formated in the response. - 🇳🇱Netherlands Lendude Amsterdam
Feels similar to 🐛 Views RSS Feed Fields adds tag. Active and probably also caused by 🐛 Allow TimestampFormatter to show as a fully cacheable time difference with JS Fixed
- 🇿🇦South Africa rudolfbyker South Africa
@Lendude those issues look similar, indeed, but they are marked as fixed, while I can still reproduce this issue by importing the attached `views.view.test.yml` file into a fresh Drupal 10.3.2 instance.
@akhil babu you are correct. With the latest Drupal version, the "Date format" is respected, but the whole thing is still wrapped in HTML. I'll update the title and description of this issue.
Partial workaround: Enable "Strip HTML tags" and "Remove whitespace" under "Rewrite results" when configuring the views field. The only problem is that it's still a string instead of an int when using "U" as the "Date format".