Add Aliases to Schedule Timer Methods for Consistent Naming

[mhomeister]

Proposal: Add Aliases to Schedule Timer Methods for Consistent Naming

Hi everyone,

I’d like to propose adding aliases to some existing schedule timer methods to improve consistency and usability, especially for non-native English speakers.

Current Situation:

Currently, we have methods like:

• everyMinute
• everyTenMinutes
• everyFourHours
• hourly
• daily
• dailyAt
• hourlyAt

While these work well, the naming conventions for hourly, daily, dailyAt, and hourlyAt differ from the everyX pattern used in other methods (e.g., everyMinute, everyTenMinutes). For developers whose native language includes terms like sekündlich or minütlich (e.g., in German), consistent naming could make the API easier to use and understand. These terms directly translate to "secondly" and "minutely," which are either uncommon or non-existent in English. However, in German and similar languages, they are valid and intuitive words.

Proposal:

Rather than renaming the existing methods, I propose adding the following aliases:

• hourly → everyHour
• daily → everyDay
• hourlyAt → everyHourAt
• dailyAt → everyDayAt
• and also weekly, monthly, yearly

This change would not break existing functionality, as the original method names (hourly, daily, hourlyAt, dailyAt) would remain intact.

Benefits:

• Improved Consistency: Aligning all method names with the everyX format improves predictability and reduces potential confusion.
• Ease of Use: Non-native English speakers may find the API more intuitive.
• Backward Compatibility: Existing codebases using hourly, daily, hourlyAt, and dailyAt will continue to work without changes.

Implementation:

• Add everyHour as an alias for hourly.
• Add everyDay as an alias for daily.
• Add everyHourAt as an alias for hourlyAt.
• Add everyDayAt as an alias for dailyAt.
• Update the documentation to include the aliases, ensuring users are aware of both naming options.

---

Looking forward to your feedback!

---