Add plugin: Diff Apply

[zlhhhh8901]

I am submitting a new Community Plugin

• I attest that I have done my best to deliver a high-quality plugin, am proud of the code I have written, and would recommend it to others. I commit to maintaining the plugin and being responsive to bug reports. If I am no longer able to maintain it, I will make reasonable efforts to find a successor maintainer or withdraw the plugin from the directory.

Repo URL

Link to my plugin: https://github.com/zlhhhh8901/obsidian-diff-apply

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 plugin'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]

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

Required

[1]
The command ID should not include the plugin ID. Obsidian will make sure that there are no conflicts with other plugins.

[1]
Use sentence case for UI text.

[1]
Avoid setting styles directly via element.style.position. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1]
Avoid setting styles directly via element.style.top. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1]
Avoid setting styles directly via element.style.left. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1]
Avoid setting styles directly via element.style.right. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1]
Avoid setting styles directly via element.style.bottom. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1]
Avoid setting styles directly via element.style.pointerEvents. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1]
Avoid setting styles directly via element.style.zIndex. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1][2][3][4]
Avoid setting styles directly via element.style.display. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1]
Avoid setting styles directly via element.style.width. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1]
Avoid setting styles directly via element.style.height. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1]
Avoid setting styles directly via element.style.overflow. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1]
Avoid setting styles directly via element.style.whiteSpace. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1]
Avoid setting styles directly via element.style.wordBreak. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1][2][3][4][5]
Avoid setting styles directly via element.style.scrollBehavior. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1]
keyCode is deprecated. MDN Reference

---

Optional

[1]
'sourceText' is assigned a value but never used.

---

Do NOT open a new PR for re-validation.
Once you have pushed some changes to your repository the bot will rescan 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.
To run these checks locally, install the eslint plugin in your project.
Do NOT rebase this PR, this will be handled by the reviewer once the plugin has been approved.

[zlhhhh8901]

Fixed ReviewBot issues and released 0.2.1. Waiting for re-scan.

[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: dreamscached/obsidian-simple-steam-auth. 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]

Changes requested by bot have been made, ready for for additional review by human.
Please be aware that it might take a few weeks before your plugin is reviewed due to the high volume of submissions currently.
Any changes you make to your repository will be automatically reviewed by the bot.