Add plugin: Smart Gantt

[nhannht]

I am submitting a new Community Plugin

Repo URL

Link to my plugin: https://github.com/nhannht/obsidian-smart-gantt

Release Checklist

• I have tested the plugin on
  • Windows
  • macOS
  • Linux
  • Android (if applicable)
  • iOS (if applicable)
• My GitHub release contains all required files
  • 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.

[ObsidianReviewBot]

The automated review has not found any issues with your code, assigning human for additional review.

[joethei]

"author": "Obsidian",
Update this.

"minAppVersion": "0.0.8",
That is way too low, set this to the latest public build number.

this.registerObsidianProtocolHandler("hello", async (_e) => {
Remove this.

this.app.workspace.detachLeavesOfType("smart-gantt")
Do not detach leaves with your custom view here, this is an antipattern, see: https://docs.obsidian.md/Plugins/Releasing/Plugin+guidelines#Don't+detach+leaves+in+%60onunload%60
Instead, only create a new leaf, if there is not one already.

return "Smart Gantt View";
Remove View here.

import mermaid from "mermaid";
Instead of importing Mermaid, use the laodMermaid function from the API, to avoid version drift.

[nhannht]

Thank you.

[github-actions]

Hello!

I found the following issues in your plugin submission

Errors:

❌ You modified files other than community-plugins.json.

---

^{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.}

[github-actions]

Hello!

I found the following issues in your theme submission

Errors:

❌ You modified files other than community-css-themes.json.
❌ The newly added entry is not at the end, or you are submitting on someone else's behalf. The last theme in the list is: Ch0live/dunite. 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.}

[nhannht]

Sorry, I cannot understand how to solve the conflict in the community-plugins.json file when if it keeps receiving changes from other sources every day. 🙇

[joethei]

You don't need to fix the merge conflicts, we will do that once the plugin is ready to be merged.

mermaid.initialize
This should not be necessary, mermaid.initialize is already being called by the loadMermaid function internally.
Or are there settings that need to be changed for the plugin to work correctly.

[nhannht]

You don't need to fix the merge conflicts, we will do that once the plugin is ready to be merged.

mermaid.initialize This should not be necessary, mermaid.initialize is already being called by the loadMermaid function internally. Or are there settings that need to be changed for the plugin to work correctly.

I don't know but we need to call mermaid.initialize with startOnLoad:true to make it work. I am not sure what happened, may be because React using an isolated environment on its own.

This new commit added a new feature that doesn't relate to old problems.

[nhannht]

I also have no idea about the error:

Error: fatal: couldn't find remote ref refs/pull/3368/merge

Follow this thread I guess I will wait for you to manually check it

[github-actions]

Hello!

I found the following issues in your plugin submission

Errors:

❌ Could not parse community-plugins.json, invalid JSON. Unexpected token < in JSON at position 4684

---

^{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.}