Add plugin: Tasks Calendar

[aviatesk]

I am submitting a new Community Plugin

Repo URL

Link to my plugin: https://github.com/aviatesk/obsidian-tasks-calendar

Release Checklist

• I have tested the plugin on
  • Windows
  • macOS
  • Linux
  • Android (if applicable)
  • iOS (if applicable)
• My GitHub release contains all required files (as individual files, not just in the source.zip / source.tar.gz)
  • main.js
  • manifest.json
  • styles.css (optional)
• GitHub release name matches the exact version number specified in my manifest.json (Note: Use the exact version number, don't include a prefix v)
• The id in my manifest.json matches the id in the community-plugins.json file.
• My README.md describes the plugin's purpose and provides clear usage instructions.
• I have read the developer policies at https://docs.obsidian.md/Developer+policies, and have assessed my plugins's adherence to these policies.
• I have read the tips in https://docs.obsidian.md/Plugins/Releasing/Plugin+guidelines and have self-reviewed my plugin to avoid these common pitfalls.
• I have added a license in the LICENSE file.
• My project respects and is compatible with the original license of any code from other plugins that I'm using.
  I have given proper attribution to these other projects in my README.md.

[github-actions]

Hello!

I found the following issues in your plugin submission

Errors:

❌ The newly added entry is not at the end, or you are submitting on someone else's behalf. The last plugin in the list is: BambusControl/obsidian-chronotyper. If you are submitting from a GitHub org, you need to be a public member of the org.

---

^{This check was done automatically. Do NOT open a new PR for re-validation. Instead, to trigger this check again, make a change to your PR and wait a few minutes, or close and re-open it.}

[ObsidianReviewBot]

Thank you for your submission, an automated scan of your plugin code's revealed the following issues:

Required

[1]:The command name should not include the plugin name.

[1]:Do not detach leaves with your custom view in onunload, this is an antipattern, see: https://docs.obsidian.md/Plugins/Releasing/Plugin+guidelines#Don't+detach+leaves+in+%60onunload%60

(Skipped)

---

Optional

[1]:Casting to any should be avoided as much as possible.

---

Do NOT open a new PR for re-validation.
Once you have pushed all of the required changes to your repo, the bot will update the labels on this PR within 6 hours.
If you think some of the required changes are incorrect, please comment with /skip and the reason why you think the results are incorrect.

[aviatesk]

/skip The parts where styles are directly specified in JavaScript are all related to rendering "tooltip" elements. In the Tasks Calendar, the position of the tooltip that pops up when an event is clicked is calculated dynamically based on the current view size and the position of the event element, so it has to be done in JavaScript. That's why we can't specify it in CSS.

All other points have been addressed.

[joethei]

this.addSettingTab(new SettingTab(this.app, this));
Your plugin does not offer any settings, you should not add a settings tab.

containerEl.createEl('h2', { text: 'Tasks Calendar Settings' });
Don't add a top-level heading in the settings tab, such as "General", "Settings", or the name of your plugin.

"Tasks Calendar", name: 'Open Tasks Calendar',, display: "Tasks Calendar",, return "Tasks Calendar";, { name: '3 Days', ,

Calendar Settings

, Task Creation Destinations, Due Date Property, Dataview Query,

Task Filtering

, "Excluded Task Statuses",, "Included Task Statuses",, "Included Task Statuses",, "Included Tags",, Delete Calendar, const modalTitle = endDate ? 'Date Range' : 'Select Date';, Clear End Date, Clear End Date, 'In Progress'
Use sentence case in UI