Skip to content

Add plugin: drive9#11948

Open
qiffang wants to merge 1 commit intoobsidianmd:masterfrom
drive9-ai:add-drive9-plugin-v2
Open

Add plugin: drive9#11948
qiffang wants to merge 1 commit intoobsidianmd:masterfrom
drive9-ai:add-drive9-plugin-v2

Conversation

@qiffang
Copy link
Copy Markdown

@qiffang qiffang commented Apr 14, 2026

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/drive9-ai/obsidian-drive9

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.

@github-actions github-actions bot changed the title Add drive9 plugin Add plugin: drive9 Apr 14, 2026
@ObsidianReviewBot ObsidianReviewBot added Changes requested Additional review required PR needs to be reviewed by another person, after the currently requested changes have been made and removed Ready for review labels Apr 14, 2026
@ObsidianReviewBot
Copy link
Copy Markdown
Collaborator

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

Required

[1]
Promise-returning method provided where a void return was expected by extended/implemented type 'Modal'.

[1]
Unexpected undescribed directive comment. Include descriptions to explain why the comment is necessary.

[1]
Disabling '@typescript-eslint/no-explicit-any' is not allowed.

[1][2][3][4][5][6][7][8][9][10][11][12][13][14][15][16][17][18][19][20][21][22][23][24][25][26][27][28][29][30][31][32][33][34][35][36][37][38][39][40]
Use sentence case for UI text.

[1][2][3][4][5][6][7][8][9][10][11]
Obsidian's configuration folder is not necessarily .obsidian, it can be configured by the user. Use Vault#configDir to get the current value

[1]
Promise returned in function argument where a void return was expected.

[1][2]
Promises must be awaited, end with a call to .catch, end with a call to .then with a rejection handler or be explicitly marked as ignored with the void operator.

[1]
For a consistent UI use new Setting(containerEl).setName(...).setHeading() instead of creating HTML heading elements directly.

[1]
Async method 'checkGitignore' has no 'await' expression.

[1][2][3]
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][2][3][4]
Avoid setting styles directly via element.style.color. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1]
Async method 'handleRemoteMissing' has no 'await' expression.


Optional

[1]
'Platform' is defined but never used.

[1]
Use 'FileManager.trashFile()' instead of 'Vault.trash()' to respect the user's file deletion preference.


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.

@qiffang
Copy link
Copy Markdown
Author

qiffang commented Apr 15, 2026

All required issues have been fixed. Ready for rescan.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Additional review required PR needs to be reviewed by another person, after the currently requested changes have been made Changes requested plugin

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants