AutoTimeBlocking feature request: Add user preference to indicate which calendars to reference when running /atb
Nadie ha tomado este issue todavía.
Evaluación
- Dificultad
- 4/5
- Tiempo estimado
- 3-5 días
- Aptitud para principiantes
- 35/100
- Tipo de issue
- Nueva funcionalidad
- Claridad
- Bastante claro
- Estado de actividad
- Estancado
- Stack tecnológico
- javascript
- Área
- desktop
Línea de trabajo
Comienza rastreando el comando /atb y la lógica de disponibilidad de calendarios de AutoTimeBlocking; después, inspecciona cómo el panel Preferences almacena la configuración del usuario. Confirma si actualmente se incluyen todos los calendarios y elige un enfoque de preferencias de inclusión o exclusión. Se considera terminado cuando la preferencia se puede configurar y /atb programa bloques usando solo los calendarios seleccionados.
Escrito por el modelo de indexación a partir del texto del issue.
Descripción
First, thank you for the AutoTimeBlocking plugin, @dwertheimer! I have just been testing it, and this is wonderful.
Is your feature request related to a problem? Please describe.
I have many "calendars" in my Calendar.app, mostly hosted and synced via iCloud, but some through other providers as well.
When I run /atb the time blocking algorithm appears to consider the content of all calendars. So, for example, if I have a shared "Family" calendar that includes things like "Kids at school from 8am to 3pm" then the /atb command thinks I am not available to start fielding tasks until 3pm, so the first time block will be placed at 3pm. This limits the usefulness of the AutoTimeBlocking plugin for me, since most days will already appear to be "fully booked", since all calendars are considered.
First, is my understanding of the logic here correct?
Second, currently, are all user calendars considered? (e.g. iCloud but also from other accounts?)
If my understanding is correct so far, then I'd request…
Describe the solution you'd like
I would love to see a user preference for specifying which calendars to consider/include when running /atb and determining availability for placing time blocks. This could be in the Preferences pane, ideally some sort of checklist where the user could tick off which calendars should be included, e.g.:
- Personal
- Work
- Family
Describe alternatives you've considered
Alternatively, it may be simpler to implement a text input box to indicate calendar names, e.g.:
Names of calendars to consider when scheduling time blocks (case-sensitive, comma separated)
Personal, Work
This is more flexible, but would require users to key in the calendar names precisely.
Another option could be to implement this as calendars to be excluded — i.e. as an ignorelist:
Names of calendars to ignore when scheduling time blocks (case-sensitive, comma separated)
Family
- Lenguaje dominante
- JavaScript
- Estrellas
- 204
- Forks
- 82
- Merge medio
- 22 h 27 min
- PR fusionados (30 d)
- 3
Guía de contribución
No hay ninguna guía de contribución indexada para este repositorio
Primeros pasos
- Lee el issue completo y luego la guía de contribución del proyecto.
- Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
- Haz un fork del repositorio y trabaja en una rama.
- Abre un pull request que haga referencia al número del issue.
Más de NotePlan/plugins
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
-
bug
Dificultad 4/5 3-5 días Aptitud para principiantes 48/100
-
Dashboard: Task "Comment" Abierto
Dificultad 5/5 Más de una semana Aptitud para principiantes 35/100
-
Tidy: Issue with plugin.json Abiertobug
-
bug
Dificultad 3/5 1-2 días Aptitud para principiantes 38/100
Todos los issues de NotePlan/plugins
Issues similares
-
code-quality refactoring
Dificultad 2/5 1-3 horas Aptitud para principiantes 84/100
github/gh-aw-firewall#8816 ·
-
integration:quickjs org:external priority:backlog topic:code-interpreter topic:middleware type:feature
Dificultad 2/5 1-3 horas Aptitud para principiantes 74/100
langchain-ai/deepagents#6450 ·
-
optimization optimization:agents-md-curator
Dificultad 2/5 1-3 horas Aptitud para principiantes 86/100
githubnext/gh-aw-cao#13143 ·
-
status: needs triage
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100
-
Dificultad 2/5 1-3 horas Aptitud para principiantes 88/100