Add plugin: Paperless

[Talal-A]

I am submitting a new Community Plugin

Repo URL

Link to my plugin: https://github.com/Talal-A/obsidian-paperless

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:

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

---

^{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]:You should change all instances of var to either const or let. var has function-level scope, so it can easily lead to bugs if you're not careful. Here's a pretty good guide with examples of why not to use var: why var is obsolete

---

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.

[ObsidianReviewBot]

Changes requested by bot have been made, ready for additional review by human.

[ObsidianReviewBot]

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

[joethei]

.overallDiv {
These class names are a bit generic, make sure they are not overwritten by other plugins by adding the plugin name as a class.

url
URL is alwas capitalized.

const folderExists = !!(this.app.vault.getAbstractFileByPath(folderPath));
This can also return true if it's a file with no extension, either do a instanceof TFolder check, or use the new getFolderByPath function (you will need to increase your minAppVersion for that)

const fileExists = !!(this.app.vault.getAbstractFileByPath(folderPath + '/' + filename));
Same here, but with instanceof TFile / getFileByPath instead.

[Talal-A]

Appreciate the feedback! I have addressed these comments in the latest release: Talal-A/obsidian-paperless@0.0.10...0.0.11

[ObsidianReviewBot]

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