| Summary: | Remove all-days range | ||
|---|---|---|---|
| Product: | [Applications] KOpeningHours | Reporter: | HubMiner <cal030> |
| Component: | normalization | Assignee: | David Faure <faure> |
| Status: | REPORTED --- | ||
| Severity: | normal | ||
| Priority: | NOR | ||
| Version First Reported In: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Other | ||
| OS: | Other | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
HubMiner
2021-11-20 03:49:02 UTC
You meant "Su" rather than "Sun" in your last example, right? I agree about minimizing unnecessary style changes, that's why we have normalizedExpression() and simplifiedExpression(). But then again, when I see "09:00-17:00" I can't help but wonder if the person actually found out which days the place was open, or if that information is missing. When I see "Mo-Su 09:00-17:00" then I'm reassured that the person found out that it was open every day. So I'm actually in favour of keeping Mo-Su or Su-Mo. Looks like we are going into human psychology with this topic. :) Based on my current OH correction experiences, I see many compound rules, for example: IN: Mo-Su 10:00-13:00; Mo-Su 14:00-20:00 OUT: Mo-Su 10:00-13:00,14:00-20:00 but perhaps day specifier is reassuring to have here as well. I guess let's skip this. |