Add plugin: Papyrus

[EdBarrancos]

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:

❌ 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: Papyrus-doc-ai/papyrus-obsidian. If you are submitting from a GitHub org, you need to be a public member of the org.
❌ The plugin ID is not valid. Only alphanumeric lowercase characters and dashes are allowed.

---

^{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][2][3][4][5][6][7]: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

[1][2][3][4]:Using innerHTML, outerHTML or similar API's is a security risk. Instead, use the DOM API or the Obsidian helper functions: https://docs.obsidian.md/Plugins/User+interface/HTML+elements

[1]:You should not cast this, instead use a instanceof check to make sure that it's actually a file/folder.

[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

[1]:Remember to rename the sample classes to something that makes sense to your plugin. If there are any errors, Obsidian will spit out this class name, so this will be important for users to debug if they need to.

---

Optional

[1][2]:Use app.fileManager.trashFile(file: TAbstractFile) instead, this will make sure that the file is deleted according to the users preferences.

---

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.

[github-actions]

Hi there, as this PR has not seen any activity in the last 30 days, it will be closed in 15 days unless there are any updates.

[EdBarrancos]

Issues in comment #4212 (comment) addressed

[ObsidianReviewBot]

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

[joethei]

/*
Remove this comment.

// If the plugin hooks up any global DOM events (on parts of the app that doesn't belong to this plugin)
Remove this sample code.

.setName("OpenAI Key"), .setName("GPT Model"), return "Papyrus Markdown Comparator Confirmator";, contentEl.createEl('h2', {text: 'Select Persona'});, .setButtonText("Start Chat"), return "CoPapyrus Tech Review";, return "Papyrus Tech Review";, techReviewSection.createEl('h1', { text: "Content Review" });, return "Papyrus Generator";, .setButtonText("Next Question")
Use sentence case in UI

.setDesc("Key to access OpenAI's apis")
It's written as API's

new Setting(containerEl)
This should not be a button, and it will do nothing.

const leaves = workspace.getLeavesOfType(viewType);
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 marked(markdown).toString();
Use MarkdownRenderer.render from the Obsidian API.