I might have a 'compose task' feature in my personal plugin. Should I propose it as a pull request? #3275
max13h
started this conversation in
Development
Replies: 1 comment 1 reply
-
Hi @max13h, Wow, from the video it looks really good. Congratulations!
That is a generous offer. Thank you. And I'm really glad that you asked before doing the work. Unfortunately I'm very busy with other work on Tasks now and for quite a few months. So I feel it's best if you keep developing it as a separate plugin, so that you have full control over what it does. Good luck, and thank you again for offering. |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello,
I'm developing a personal plugin to optimize my workflow.
As an Obsidian mobile power user, I’ve found it challenging to use the task-plugin and day-planner-plugin together, particularly when correcting or adjusting times (a feature of day-planner).
To address this, I wrote a plugin with a command called "Add Task." This command prompts me with options to create a task, focusing only on the task properties "schedule", times and content since those are the ones I primarily use.
I also wrote my own task parser using the Dataview plugin API.
My question is: Would this feature align with the evolution of the task-plugin? Should I invest time in proposing it as a pull request?
My plugin repo:
https://github.com/max13h/max13h-plugin
Feature preview:
https://github.com/user-attachments/assets/2dc437bf-94c5-4510-ab93-eca5b3999df8
As a junior developer, this would be my first contribution to an open-source project. I’d appreciate any advice or feedback you might have. 😊
Thank you for you work, I use this plugin every day and it makes my life easier
Beta Was this translation helpful? Give feedback.
All reactions