Skip to content

Conversation

kuzzh
Copy link
Contributor

@kuzzh kuzzh commented Jul 3, 2025

I am submitting a new Community Plugin

Repo URL

Link to my plugin: https://github.com/kuzzh/obsidian-startpage

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.

@ObsidianReviewBot
Copy link
Collaborator

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


Optional

[1][2]:Casting to any should be avoided as much as possible.


Do NOT open a new PR for re-validation.

@ObsidianReviewBot ObsidianReviewBot removed their assignment Jul 4, 2025
@kuzzh
Copy link
Contributor Author

kuzzh commented Jul 4, 2025

/skip

Regarding the suggestions under Optional, they may not be changeable due to specific techniques I had to use to implement the desired functionality.

For suggestion [1], I can’t directly access the state object from leaf.view, nor can I cast it to a MarkdownView to gain access—it appears to be a non-public property. Since accessing it is essential for my feature, I had no choice but to cast it as any.

As for suggestion [2], the reasoning is similar: the setting object isn’t exposed by the app, but I need access to it in order to directly open my plugin’s settings page. So again, casting it as any was necessary.

@github-actions github-actions bot added the Skipped code scan Code scanning skipped because submission is not in TS/author believes result is wrong label Jul 4, 2025
@kuzzh kuzzh force-pushed the patch-1 branch 2 times, most recently from 6efbb40 to a475ff5 Compare July 5, 2025 01:32
Copy link

github-actions bot commented Jul 5, 2025

Hello!

I found the following issues in your plugin submission

Errors:

❌ You modified files other than community-plugins.json.


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.

Copy link

github-actions bot commented Jul 6, 2025

Hello!

I found the following issues in your plugin submission

Errors:

❌ You modified files other than community-plugins.json.


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.

Copy link

github-actions bot commented Jul 6, 2025

Hello!

I found the following issues in your plugin submission

Errors:

❌ You modified files other than community-plugins.json.


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.

Copy link

github-actions bot commented Jul 6, 2025

Hello!

I found the following issues in your plugin submission

Errors:

❌ You modified files other than community-plugins.json.


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
Copy link
Collaborator

The automated review has not found any issues with your code, ready for manual review.
Please be aware that it might take a few weeks before your plugin is reviewed due to the high volume of submissions currently.

kuzzh and others added 23 commits August 28, 2025 09:01
Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts
Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts
Resolve branch cannot be rebased due to conflicts
Resolve branch cannot be rebased due to conflicts
Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts

Resolve branch cannot be rebased due to conflicts
Resolve branch cannot be rebased due to conflicts
Resolve branch cannot be rebased due to conflicts
Resolve branch cannot be rebased due to conflicts
Resolve branch cannot be rebased due to conflicts
Resolve branch cannot be rebased due to conflicts
Resolve branch cannot be rebased due to conflicts
Resolve branch cannot be rebased due to conflicts
Resolve branch cannot be rebased due to conflicts
Resolve branch cannot be rebased due to conflicts
Resolve branch cannot be rebased due to conflicts
Resolve branch cannot be rebased due to conflicts
Resolve branch cannot be rebased due to conflicts
Resolve branch cannot be rebased due to conflicts
@ObsidianReviewBot
Copy link
Collaborator

The automated review has not found any issues with your code, ready for manual review.
Please be aware that it might take a few weeks before your plugin is reviewed due to the high volume of submissions currently.

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

Successfully merging this pull request may close these issues.