obsidian-releases
obsidian-releases copied to clipboard
Add plugin: Expense Tracker
I am submitting a new Community Plugin
Repo URL
Link to my plugin: https://github.com/mayankkushal/obsidian-expense-tracker
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
.
Hello!
I found the following issues in your plugin submission
Errors:
:x: The authorUrl
field in your manifest should not point to the Obsidian Website. If you don't have a website you can just point it to your GitHub profile.
:x: The fundingUrl
field in your manifest should not point to the Obsidian Website, If you don't have a link were users can donate to you, you can just omit this.
:x: Unable to find a release with the tag 0.0.10
. Make sure that the version in your manifest.json file in your repo points to the correct Github Release.
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.
Thank you for your submission, an automated scan of your plugin code's revealed the following issues:
[1][2][3][4][5]: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][2][3][4][5][6][7][8][9][10][11]:Casting to any
should be avoided as much as possible.
Do NOT open a new PR for re-validation. 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.
Once you have pushed all of the required changes, the bot will reevaluate your PR within 4 hours.
Hello!
I found the following issues in your plugin submission
Errors:
:x: 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: luxmargos/obsidian-canvas-card-bg-remover
. 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.
Hello!
I found the following issues in your plugin submission
Errors:
:x: Could not parse community-plugins.json
, invalid JSON. Unexpected token ] in JSON at position 359765
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.
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.
/skip - Fixed most of the issues, BOT not triggered again
Hello!
I found the following issues in your plugin submission
Errors:
:x: Could not parse community-plugins.json
, invalid JSON. Unexpected token { in JSON at position 359748
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.
/skip - previous run failed
@joethei add assignee is failing
// Perform additional things with the ribbon Remove this code.
new Setting(containerEl).setName("Ledger Path").addText((text) =>, .setName("Check Interval (sec)"), ["Date", "Description", "To Account", "From Account", "Total"].forEach( Use sentence case in UI
this.plugin.settings.checkIntervalSec = Number(value); You should add some error handling here, or use a slider to input the number.
el.innerHTML = "";
Use el.empty()
instead.
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!