Add plugin: Aiob Board

[Aioblifeos]

I am submitting a new Community Plugin

• I attest that I have done my best to deliver a high-quality plugin, am proud of the code I have written, and would recommend it to others. I commit to maintaining the plugin and being responsive to bug reports. If I am no longer able to maintain it, I will make reasonable efforts to find a successor maintainer or withdraw the plugin from the directory.

Repo URL

Link to my plugin: https://github.com/Aioblifeos/obsidian-aiob-board

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 plugin'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:

❌ You did not follow the pull request template. The PR template can be found here
❌ Please don't include Obsidian in the plugin description
❌ Unable to find a release with the tag 1.0.0. 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.}

[github-actions]

Hello!

I found the following issues in your plugin submission

Errors:

❌ You did not follow the pull request template. The PR template can be found here

---

^{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]
Use sentence case for UI text.

[1][2]
Promises must be awaited, end with a call to .catch, end with a call to .then with a rejection handler or be explicitly marked as ignored with the void operator.

[1][2]
The command name should not include the plugin name, the plugin name is already shown next to the command name in the UI.

[1]
Promise-returning method provided where a void return was expected by extended/implemented type 'Plugin'.

[1]
Async method 'onunload' has no 'await' expression.

[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][31][32][33][34][35][36][37][38][39][40][41][42][43][44][45][46][47][48][49][50][51][52][53][54][55][56][57][58][59][60][61][62][63][64][65][66][67][68][69][70][71][72][73][74][75][76][77][78][79][80][81][82][83][84][85][86][87][88][89][90]
Unexpected any. Specify a different type.

[1][2][3][4][5]
This assertion is unnecessary since it does not change the type of the expression.

[1]
'value ?? ''' will use Object's default stringification format ('[object Object]') when stringified.

[1][2][3][4][5][6][7][8][9][10][11][12][13][14][15][16][17][18][19][20][21][22][23]
Promise returned in function argument where a void return was expected.

[1][2][3]
Creating and attaching "style" elements is not allowed. For loading CSS, use a "styles.css" file instead, which Obsidian loads for you.

[1][2][3][4][5][6]
Avoid setting styles directly via element.style.color. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1][2][3]
Avoid setting styles directly via element.style.borderRadius. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1][2]
Avoid setting styles directly via element.style.padding. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1][2]
Avoid setting styles directly via element.style.margin. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1][2][3][4]
Avoid setting styles directly via element.style.border. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1][2][3]
Avoid setting styles directly via element.style.backgroundColor. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1]
Async method 'resolveTargetFileForDate' has no 'await' expression.

[1]
Unexpected console statement. Only these console methods are allowed: warn, error, debug.

[1]
Unnecessary escape character: \】.

[1]
Async method 'onOpen' has no 'await' expression.

[1]
Async method 'onClose' has no 'await' expression.

[1]
Avoid setting styles directly via element.style.backgroundSize. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1][2]
Empty block statement.

[1][2]
Avoid setting styles directly via element.style.height. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1][2][3]
Unexpected use of 'localStorage'. Prefer App#saveLocalStorage / App#loadLocalStorage functions to write / read localStorage data that's unique to a vault.

[1][2]
Promise-returning function provided to property where a void return was expected.

[1][2]
Avoid setting styles directly via element.style.position. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1]
Avoid setting styles directly via element.style.left. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1]
Avoid setting styles directly via element.style.opacity. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1]
Avoid setting styles directly via element.style.right. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1]
Avoid setting styles directly via element.style.bottom. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1]
Avoid setting styles directly via element.style.display. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

---

Optional

[1]
'Notice' is defined but never used.

[1]
'TFile' is defined but never used.

[1]
'TFolder' is defined but never used.

[1][2]
Use 'FileManager.trashFile()' instead of 'Vault.delete()' to respect the user's file deletion preference.

[1]
Use 'FileManager.trashFile()' instead of 'Vault.trash()' to respect the user's file deletion preference.

---

Do NOT open a new PR for re-validation.
Once you have pushed some changes to your repository the bot will rescan 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.
To run these checks locally, install the eslint plugin in your project.
Do NOT rebase this PR, this will be handled by the reviewer once the plugin has been approved.