Skip to content

Conversation

@Reifat
Copy link

@Reifat Reifat commented Nov 9, 2025

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/Reifat/daily-notes-sorter

Release Checklist

  • I have tested the plugin on
    • Windows
    • macOS
    • Linux
    • Android
    • iOS
  • 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.
  • [xq] 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
Copy link

github-actions bot commented Nov 9, 2025

Hello!

I found the following issues in your plugin submission

Errors:

❌ Description mismatch, the description in this PR (Automatically sort daily notes by date in the file explorer.) is not the same as the one in your repo (Automatically sort daily notes and files by date in the file explorer. Supports multiple date formats (YYYY-MM-DD, DD.MM.YYYY, DD.MM.YY, MM/DD/YYYY) and flexible folder configuration.). If you just changed it, remember to change it in the manifest.json in your repo and your latest GitHub release.
❌ 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.

@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 Nov 9, 2025
@ObsidianReviewBot
Copy link
Collaborator

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]
Unexpected any. Specify a different type.

[1]
Unexpected aliasing of 'this' to local variable.

[1]
'moment' import is restricted from being used. The 'moment' package is bundled with Obsidian. Please import it from 'obsidian' instead.

[1]
Unexpected undescribed directive comment. Include descriptions to explain why the comment is necessary.

[1]
Disabling '@typescript-eslint/no-explicit-any' is not allowed.

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

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

[1]
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]
For a consistent UI use new Setting(containerEl).setName(...).setHeading() instead of creating HTML heading elements directly.

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

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

[1]
An empty interface declaration allows any non-nullish value, including literals like 0 and "".

  • If that's what you want, disable this lint rule with an inline comment or configure the 'allowInterfaces' rule option.
  • If you want a type meaning "any object", you probably want object instead.
  • If you want a type meaning "any value", you probably want unknown instead.

Optional

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

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

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

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

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

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

[1]
'PluginInstance' is defined 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.

@ObsidianReviewBot
Copy link
Collaborator

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

Required

[1]
Unexpected aliasing of 'this' to local variable.

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

[1]
activeLeaf is deprecated. The use of this field is discouraged.
The recommended alternatives are:

  • If you need information about the current view, use {@link Workspace.getActiveViewOfType}.
  • If you need to open a new file or navigate a view, use {@link Workspace.getLeaf}.

[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]
For a consistent UI use new Setting(containerEl).setName(...).setHeading() instead of creating HTML heading elements directly.


Optional

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

[1]
'moreItem' 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