Either as an expansion of an existing formatter or a new formatter, it should be possible to output events that repeat multiple times a day in a way that is more optimized. For example, grouped by day, listing only the times.
Potential features:
- Group hourly, minutely recurring events by day
- "Daily" listing that is not date specific?
- configure days in the the past, future to show
- option to show only start time for each instance
- show duration if overridden?
- option to show date inline vs above?
| Comment | File | Size | Author |
|---|---|---|---|
| #6 | smart_date-hourly_formatting-3176302-6.patch | 15.18 KB | mandclu |
Comments
Comment #2
mandclu commentedComment #3
mandclu commentedFirst attempt at implementing this, for both recurring-optimized formatters. Essentially, when dealing with a recurrence rule less than a day, the day is counted as an instance, and all the instances listed for the day.
Comment #4
mrpauldriver commentedAfter patching I am unable to view the manage display page at admin/structure/types/manage/event/display
Attempting to do result in a fatal error, with message below;
Fatal error : Trait 'Drupal \ smart_date_recur \ SmartDateRecurTrait' not found in /var/www/html/web/modules/contrib/smart_date/modules/smart_date_recur/src/Plugin/Field/FieldFormatter/SmartDateDateDailyRangeFormatter.php on line 30 .phpComment #5
mandclu commentedWhoops, new patch to include the missing file.
Comment #6
mandclu commentedFound another small issue in my own testing, new patch.
Comment #7
mrpauldriver commentedI was seeing problems with the patch#5, but find that #6 applies without problems and the new display I see for the Daily Range and Recurring formatters is similar to that in the screenshot from #3
I think this works well, but it occurs to me that some uses cases may need a more complete listing, like that provided by the Smart Date Formatter and the same with duration.
More feedback from real usage in production would be helpful.
Comment #9
mandclu commentedThat's a very valid perspective, but I know for myself I'd be cautious to use alpha-stability code in production. Merging in what we have for now, and will move the 3.1.x branch to a beta release. Please open a child issue if you have additional ideas on how this could be improved.