diffInOpenMinutes() does not work if only one day is configured as open about opening-hours HOT 6 CLOSED

Catching the exception is not a solution, we could also just never throw it. But there is a good reason for it to be there, it prevents infinite loops that you would hit if you actually try to find nextOpen() => there is nothing to find in the future, so it would search forever, that's why there is this exception.

You can increase the limit to your convenience: setDayLimit(), you can try $openingHours->setDayLimit(PHP_INT_MAX) at your own risks.

from opening-hours.

I fully understand why in general the exception is thrown. But here in this case, only in this function, it leads to an error as described. You cannot calculate diffInOpenMinutes, when there is only one possible date.

from opening-hours.

Sorry. Indeed I see your point. We can catch in diffInSeconds and consider that a closing time within the limit, then the whole period is open.

from opening-hours.

In my example configuration opening hours are defined like this:
'2016-11-11' => ['09:00-12:00']
So when I call $openingHours->diffInOpenMinutes('2016-11-01', '2016-11-31') I expect to get 180 minutes.
In the loop the $skipDateMethod='nextOpen' will not find anything after 2016-11-12 and therefore throw the exception, but the sum of the time is already 180 minutes. So it makes sense for me to return that time.

from opening-hours.

Fixed in the version 2.41.0

from opening-hours.

Great thanks, its working now.

from opening-hours.