Add plugin: Gamificate your PKM

[saertna]

I am submitting a new Community Plugin

Repo URL

Link to my plugin: obsidian-gamified-pkm

Release Checklist

• I have tested the plugin on
  • Windows
  • macOS
  • Linux
  • Android (if applicable)
  • iOS (if applicable)
• My GitHub release contains all required files
  • 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 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.

[joethei]

Please remove the main.js file from the repo and add it to your .gitignore - compiled release files shouldn't get mixed with source code in your commits and should go to the releases files instead.

"styles": ["styles.css"]
This is not part of the manifest spec.

const style = document.createElement('style');
This should be part of the styles.css file.

getSettingString(key: string) {
Is there a reason why you are encryption the settings values?
It feels pointless, since the data is not confidential.

name: 'open booter pallete',
It looks like there is a typo here, as the id is boosters

"Calculate Note Maturity" and many more.
Use sentence case in UI

console.log(note-maturity >=1) and more
Please avoid unnecessary logging. If you need it for debugging purposes, add a check to only log during development.

fs.readdirSync(dir);
Instead of using the fs API you should use the vault API.

path.join(dir, file)
Just join the two with a simple /, together with the change above, this code will now be mobile compatible.

stockInfo.innerHTML += ${this.getIngerementFromName(element).shortName} [${this.remainingStock[this.getIngerementFromName(element).name] || 0}]      ;, and more.
Avoid using innerHTML

const coffeeDiv = containerEl.createDiv("coffee");
This should not be the very first thing a user sees.

containerEl.createEl('h2', { text: 'General' });
Don't use a "general" heading in your settings

export function isTFile(value: TAbstractFile): value is TFile {
use a instanceof check instead.

[github-actions]

Hello!

I found the following issues in your plugin submission

Errors:

❌ 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: shumpei-tanaka/obsidian-short-tab-name. 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.}

[saertna]

@joethei, I fixed all you findings. Your listing was of great help to work through the code and improve it.
You are rigth, data.json contains no confidential data. The gamification get's pointless if you just need to edit the data.json to reach levels, get boosters and so an. To prevent the 'player' looses motivation by just cheating himself, it's encrypted. That's the only backgroud for encrypting data.json.

[github-actions]

Hello!

I found the following issues in your plugin submission

Errors:

❌ Could not parse community-plugins.json, invalid JSON. Unexpected token : in JSON at position 315954

---

^{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.}

[github-actions]

Hello!

I found the following issues in your plugin submission

Errors:

❌ Could not parse community-plugins.json, invalid JSON. Unexpected token } in JSON at position 316405

---

^{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.}

[liamcain]

@saertna No need to keep rebasing the plugin. I will rebase the pull request after it gets approved.

[saertna]

Ah, thanks for letting me know @liamcain.