Rationalise some Event-related plugin and commands
@dwertheimer is already working on this.
Since May 27, 2022.
- Dominant language
- JavaScript
- Stars
- 204
- Forks
- 82
- Avg merge
- 22h 27m
- Merged PRs (30d)
- 3
Description
We have many excellent commands in plugins. But inevitably they have grown up without planning, as different authors have seen different (but related) needs. This issue is to discuss doing some rationalisation. An OK outcome is to decide to make no changes, but at least let's discuss them.
| Command | Current Plugin | Future Plugin? |
|---|---|---|
| /time blocks to calendar | Event Helpers | Time Block Helpers (new) |
| /atb | AutoTimeBlocking | Time Block Helpers |
| Create ATB using Presets | AutoTimeBlocking | Time Block Helpers |
| rest of EventHelpers commands | Event Helpers | Event Helpers (i.e. no change) |
In practice, this would mean dropping 'AutoTimeBlocking' unless we can rename it to 'Time Block Helpers'.
Hmm, fewer things to change than I thought. No matter. What do you think @dwertheimer?
I've not implemented Reminders commands, but I know others are keen to have them. I've left this as an exercise for others, as I don't use reminders myself. But if we do get them, then they could either live in a parallel 'Reminders Helpers' plugin, or extend 'Event Helpers' to 'Events & Reminders'.
And do you have any plans, @nmn @oschrenk @mikeerickson @m1well or others related to Events, Reminders, Time Blocks?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.