obsidian-releases
obsidian-releases copied to clipboard
Add better-inline-fields plugin
I am submitting a new Community Plugin
Repo URL
Link to my plugin: https://github.com/dsarman/better-inline-fields
Release Checklist
- [x] I have tested the plugin on
- [ ] Windows
- [x] macOS
- [ ] Linux
- [ ] Android (if applicable)
- [ ] iOS (if applicable)
- [ ] 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 tips in https://github.com/obsidianmd/obsidian-releases/blob/master/plugin-review.md 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
.
Hello dsarman! ![](https://user-images.githubusercontent.com/59741989/139557624-63e6e31f-e617-4041-89ae-78b534a8de5c.png)
I found the following errors in your plugin, Commander:
:x: The newly added entry is not at the end, or you are submitting on someone else's behalf. Last plugin in the list is: phibr0/obsidian-commander
This check was done automatically.
As your plugin uses Dataview you should add a notification somwhere, either as a notice or in the settings if Dataview is not installed/enabled.
Agree with joethei's comment. It would be useful to add a check when the plugin loads to make sure that dataview is installed.
Thanks for the approve and for the suggestion. I added a notice to the plugin's settings page if Dataview is not enabled.