Skip to content

Add plugin: Lite Calendar#11934

Open
fengshuzi wants to merge 1 commit intoobsidianmd:masterfrom
fengshuzi:add-lite-calendar
Open

Add plugin: Lite Calendar#11934
fengshuzi wants to merge 1 commit intoobsidianmd:masterfrom
fengshuzi:add-lite-calendar

Conversation

@fengshuzi
Copy link
Copy Markdown

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/fengshuzi/lite-calendar

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.

@ObsidianReviewBot ObsidianReviewBot added Changes requested Additional review required PR needs to be reviewed by another person, after the currently requested changes have been made and removed Ready for review labels Apr 14, 2026
@ObsidianReviewBot
Copy link
Copy Markdown
Collaborator

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

Required

[1]
Unexpected use of 'app'. Avoid using the global app object. Instead use the reference provided by your plugin instance.

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

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

[1][2][3][4]
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]
Promise-returning method provided where a void return was expected by extended/implemented type 'Plugin'.

[1]
Don't detach leaves in onunload, as that will reset the leaf to it's default location when the plugin is loaded, even if the user has moved it to a different location.

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

[1][2][3][4][5][6]
Unexpected any. Specify a different type.

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

[1][2][3][4][5][6][7][8][9][10][11][12][13][14][15]
Avoid setting styles directly via element.style.display. 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.fontSize. 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.color. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

[1]
Avoid setting styles directly via element.style.marginBottom. 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]
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]
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]
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]
Avoid setting styles directly via element.style.marginTop. Use CSS classes for better theming and maintainability. Use the setCssProps function to change CSS properties.

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

[1][2][3][4]
Do not write to DOM directly using innerHTML/outerHTML property

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

[1]
Unexpected confirm.


Optional

[1]
'option' is assigned a value but never used.

[1]
'year' is assigned a value but never used.


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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Additional review required PR needs to be reviewed by another person, after the currently requested changes have been made Changes requested plugin

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants