obsidian-releases
obsidian-releases copied to clipboard
Add plugin: AI Note Suggestion
I am submitting a new Community Plugin
Repo URL
Link to my plugin: https://github.com/echo-saurav/obsidian-ai-note-suggestion
Release Checklist
- [ ] I have tested the plugin on
- [ ] Windows
- [x] macOS
- [ ] Linux
- [ ] Android (if applicable)
- [x] iOS (if applicable)
- [x] My GitHub release contains all required files
- [x]
main.js
- [x]
manifest.json
- [x]
styles.css
(optional)
- [x]
- [x] 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
) - [x] The
id
in mymanifest.json
matches theid
in thecommunity-plugins.json
file. - [x] My README.md describes the plugin's purpose and provides clear usage instructions.
- [x] I have read the developer policies at https://docs.obsidian.md/Developer+policies, and have assessed my plugins's adherence to these policies.
- [x] 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.
- [x] I have added a license in the LICENSE file.
- [x] 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
.
Thank you for your submission, an automated scan of your plugin code's revealed the following issues:
[1][2]:You should avoid assigning styles via JavaScript or in HTML and instead move all these styles into CSS so that they are more easily adaptable by themes and snippets.
[1][2]: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.
[1][2][3][4][5][6][7]:You should not cast this, instead use a instanceof
check to make sure that it's actually a file/folder
[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]:You should consider limiting the number of console.log
s in your code, to not pollute the dev console.
Do NOT open a new PR for re-validation.
Once you have pushed all of the required changes, the bot will reevaluate your PR within 6 hours.
If you think some of these results are incorrect, please include /skip
in your comment and the reason why you think the results are incorrect.
Hi there, as this PR has not seen any activity in the last 30 days, it will be closed in 30 days unless there are any updates.
"description": "This plugin shows semantically related notes and filer notes by tags using power of A.I (Vector search)", Avoid including sentences like "This plugin does ..." in your description, it should be self-evident that this is a plugin for Obsidian. 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.
"authorUrl": "", Fill this, if you don't have a website use your GitHub profile.
"fundingUrl": "", This is meant for links to services like Buy me a coffee, GitHub sponsors and so on, if you don't have such a link omit this.
export const GetOnNoteViewExtension = (myPlugin: MyPlugin) =>, constructor(leaf: WorkspaceLeaf, myplugin: MyPlugin) { Update the type for your plugin.
export class MySettings extends PluginSettingTab { Rename this class.
.setName('Weaviate Address'), .setName('Suggestion Limit'), .setName('Similarity Distance'), .setName('Enable Autocut') Use sentence case in UI
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.
Hi there, to keep things tidy, we're closing PRs after one and a half months of inactivity. Feel free to create a new pull request when you're ready to continue. Thanks for your understanding!