Add plugin: Confluence Converter

[addozhang]

I am submitting a new Community Plugin

Repo URL

Link to my plugin:

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:

❌ Please don't include Obsidian in the plugin description

---

Warnings:

⚠️ Your repository does not have issues enabled. Users will not be able to report bugs and request features.

---

^{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 plugin submission

Errors:

❌ Please don't include Obsidian in the plugin description
❌ Unable to find a release with the tag 0.1.0. Make sure that the version in your manifest.json file in your repo points to the correct Github Release.

---

Warnings:

⚠️ Your repository does not have issues enabled. Users will not be able to report bugs and request features.

---

^{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 plugin submission

Errors:

❌ Unable to find a release with the tag 0.1.0. Make sure that the version in your manifest.json file in your repo points to the correct Github Release.

---

Warnings:

⚠️ Your repository does not have issues enabled. Users will not be able to report bugs and request features.

---

^{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 plugin submission

Errors:

❌ Unable to find a release with the tag 0.1.0. Make sure that the version in your manifest.json file in your repo points to the correct Github Release.

---

Warnings:

⚠️ Your repository does not have issues enabled. Users will not be able to report bugs and request features.

---

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

[addozhang]

❌ Unable to find a release with the tag 0.1.0. Make sure that the version in your manifest.json file in your repo points to the correct Github Release.

tag 0.1.0 created

[ObsidianReviewBot]

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

---

Optional

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

---

Do NOT open a new PR for re-validation.

[addozhang]

The casting issue was fixed.

[ObsidianReviewBot]

The automated review has not found any issues with your code, ready for manual review.

[joethei]

# Obsidian Confluence Toolkit Plugin
Naming something "Obsidian xyz" is reserved for first party products we create, please change this header.

This project is licensed under the MIT License.
You need to copy the license text into this file.

"description": "An plugin for converting markdown to Confluence wiki markup.",
Avoid including sentences like "This is a plugin that does ..." in your description, it should be a given since this is only shown when browsing plugins through the app or on our website.
We have published a guide for plugin descriptions to follow here: https://docs.obsidian.md/Plugins/Releasing/Submission+requirements+for+plugins#Keep+plugin+descriptions+short+and+simple.

name: 'Convert to Confluence and Copy to Clipboard',, .setName("CodeBlock Theme"), .setName("Show Line Numbers"), .setName("Collapse Code Block")
Use sentence case in UI

console.log("parsed tokens",tokens)
Please avoid unnecessary logging. If you need it for debugging purposes, add a check to only log during development.

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

[addozhang]

@joethei Thanks for your advice. I have updated following your comments. Please take a review again.

[github-actions]

Hello!

I found the following issues in your plugin submission

Errors:

❌ Could not parse community-plugins.json, invalid JSON. Expected ',' or ']' after array element in JSON at position 541990

---

^{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 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: t5k6/obsidian-koreader-highlights. 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.}

[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: t5k6/obsidian-koreader-highlights. 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.}