Recurring Formatter: have "next instance" default to most recent if all in the past

I considered making it a separate issue, but this seemed similar enough...

The recurring date formatter also seems to consider actively current events, e.g. events where the start time is before "now" and the end time is after, to be "recent".

e.g. as I am posting this, it is 5:20 pm on April 19th. I created an event in the starter kit modified to use recurring dates. I would like to be able to include a current date under upcoming. This also seems to affect "All-day" events.

Event with start and end times recurring today

Weekly on Monday at 10:00am for 4 times
RECENT

• Mon, Apr 19 2021, 10am - 11pm

UPCOMING

• Mon, Apr 26 2021, 10am - 11pm
• Mon, May 3 2021, 10am - 11pm
• Mon, May 10 2021, 10am - 11pm

Edit:

I am able to extend SmartDateRecurrenceFormatter and replace findNextInstance() with this snippet:

      $values = $instance->getValue();
      if ($end = $values['end_value']) {
        if ($end > $time) {
          $next_index = $index;
          break;
        }
      }
      else {
        if ($instance->value > $time) {
          $next_index = $index;
          break;
        }
      }

One note, these are private methods, so I need to re-implement the whole class, instead of extending it, and overriding the methods I need.

Just jumping in to say I have the same need as @bburg above: I want events that are currently underway to display as upcoming, not "recent", and I came up with the same solution - extending SmartDateRecurrenceFormatter.

However in my case instead of reimplementing the entire class I've added a patch to my composer so that it makes the two methods protected rather than private. Long term, it would be nice if this could either be an option on the formatter, or if those methods could be made protected permanently.

Well, I'm not sure how much use this will be to anyone else, but I've attached the patch that sets the two methods I override in my formatter as protected. (I did read the Drupal "Making a patch" guide but I apologise if this file is unsuitable in any way.)

This does not fix either of the problems in this issue but it does make it easier for a developer to override it.

Sorry, I only just got the chance to test this out! I just installed 3.4@beta and it works exactly as described, thanks very much for this.