Summary
The date_groups key in config/activity-log.php is unused. The buckets a user sees in the timeline are computed by ActivityLogLivewire::bucketFor and ignore config entirely.
Repro
grep -r "date_groups" src/
# (no matches)
The lang file resources/lang/en/messages.php only ships keys for this_week, last_week, week_of — matching what bucketFor() actually emits.
Expected vs actual
- Documented (and currently shipped in
config/activity-log.php): 6 bucket labels (today, yesterday, this_week, last_week, this_month, older).
- Reality: 3 buckets emitted by the Livewire component (
this_week, last_week, week_of <date>).
Recommended fix
Choose one:
- Delete the key from
config/activity-log.php and document the bucketing as fixed.
- Wire the key into
bucketFor() so users can customize bucket labels and grouping windows.
Option 1 is lower-risk and matches current behavior. Option 2 is the more ambitious feature.
Tracked by docs spec
Finding A1 in the upcoming docs restructure.
Summary
The
date_groupskey inconfig/activity-log.phpis unused. The buckets a user sees in the timeline are computed byActivityLogLivewire::bucketForand ignore config entirely.Repro
The lang file
resources/lang/en/messages.phponly ships keys forthis_week,last_week,week_of— matching whatbucketFor()actually emits.Expected vs actual
config/activity-log.php): 6 bucket labels (today,yesterday,this_week,last_week,this_month,older).this_week,last_week,week_of <date>).Recommended fix
Choose one:
config/activity-log.phpand document the bucketing as fixed.bucketFor()so users can customize bucket labels and grouping windows.Option 1 is lower-risk and matches current behavior. Option 2 is the more ambitious feature.
Tracked by docs spec
Finding A1 in the upcoming docs restructure.