Add plugin: Spaceforge

[dralkh]

I am submitting a new Community Plugin

Repo URL

Link to my plugin: https://github.com/dralkh/spaceforge

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

Hello!

I found the following issues in your plugin submission

Errors:

❌ The authorUrl field in your manifest should not point to the GitHub repository of the plugin.
❌ Your latest release is missing the main.js file.
❌ Your latest release is missing the manifest.json file.

---

^{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]

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

Required

[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] and more :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][3]: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]:We recommend against providing a default hotkey when possible. The reason being that it's easy to pick a hotkey that a user already has configured and they could get confused when that key doesn't do what they expect. Also, it's hard choosing a safe default hotkey that's available for all operating systems.

[1]:Do not detach leaves with your custom view in onunload, this is an antipattern, see: https://docs.obsidian.md/Plugins/Releasing/Plugin+guidelines#Don't+detach+leaves+in+%60onunload%60

[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] and more :You should consider limiting the number of console.logs in your code, to not pollute the dev console.

---

Optional

[1][2][3][4][5][6][7][8][9][10]:Casting to any should be avoided as much as possible.

[1][2][3][4]:Obsidian provides the requestUrl method, it will make sure that network requests work on every plattform.

---

Do NOT open a new PR for re-validation.
Once you have pushed all of the required changes to your repo, the bot will update the labels on this PR 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.

[dralkh]

/skip more than 6 hours passed since update from repo